Your code.
Your feedback.

Yes! Read more here.

The Sprkl Operator is an improvement of the OpenTelemetry Operator. The OpenTelemetry Operator applies automatic library and infrastructure-level instrumentation. The Sprkl Operator provides the same functionality and integrates Sprkl instrumentation with it. Together Sprkl brings you cluster-level distributed tracing with personalization on your Node.js services. Read more on our docs.

By using Sprkl, you immediately understand how your code performs. You no longer need to spend time manually collecting data and trying to piece it all together. No more sifting through endless logs or traces, adding breakpoints, or switching from one tool to another. Sprkl helps you research, plan, debug, test, and prevent issues, and investigate existing issues faster so you can focus on writing your best possible code. 

Sprkl is a Personal Observability platform that provides personalized feedback on your code changes while coding. Sprkl helps ship correct and efficient code while spending less time on debugging, code review, and frustrating rework. Powered by OpenTelemetry, Sprkl instruments every code change and analyzes it upon execution. Watch Sprkl feedback while coding (VSCode/ web / during CI).

Watch a short Sprkl demo here.

Using sprkl with TypeScript is as easy as using it for native Javascript. Just make sure that you enable sourcemaps when building the code, and that the sourcemaps are available when running sprkl (either as files with the compiled code or inlined).
Example using esbuild: esbuild –sourcemap …
Example using tsc (tsconfig.json):

Of course. Sprkl can instrument any git recipe you can think of. For example, you can instrument or exclude: uncommitted changes, my commits only; all commits since I left the main branch; all commits in the last six months, etc. Those are configurable.

No. It comes out of the box: you don’t need to deal with the hassle of installing it.

We instrument your code change alone, instead of your entire codebase. The instrumentation will only be applied to the specific part of your code that you want to instrument, not to your whole codebase and will not affect staging or production modes. 

No. Sprkl doesn’t change your code functionality or files.

We don’t change your code’s functionality in any way. Instead, we add an instrumentation layer to your code that only runs on your local machine. We use our intelligent instrumentation engine to leverage OpenTelemetry (a typical, trustworthy open-source project) to apply our instrumentation to your code automatically.

Node.js v16.10 and up (Java, C#, and Python are partially supported via our Kubernetes Setup). We gradually adding support for additional languages. Please tell us what you’d like us to support:Here.

Sprkl for GitHub Actions shortens code reviews and debugging time by providing a focused, personalized report for every Pull Request. See deeper into the effects of your code diff, including hidden errors, app ripple effect, performance and security insights, diff coverage and more. Read more on our docs or join for free here. 

Yes! Sprkl ships with Jest testing instrumentation (unit and integration tests), providing insights and traces for every execution. You can get an overview of the execution of your tests, including details for mocks and assertions. Get a better understanding of what is tested (or not tested) for the code changes you analyze. Read more here or this article in our blog.

Yes! Sprkl works with Kubernetes and provides auto instrumentation with both OpenTelemetry and Sprkl instrumentation for all the services in the cluster. Check out how to use Sprkl for Kubernetes here.

We leverage OpenTelemetry to automatically instrument every code change and analyze it upon execution. Read our docs to learn more.

Sprkl currently supports Node v16.1.0 or higher. 

TBA soon – we’re working on it.

No, unless you really want to :). We think it’s TMI and isn’t helpful. We want to help you focus on what matters.

Sprkl for CI (new) enables you to see Sprkl info in CI/CD. We’ll gradually support staging and production environments. We aim to show you how your code changes function throughout the entire lifecycle.

We focus on what you need to see to ship better code faster. Therefore, we focus on what is relevant to your own code change – how it affects and is affected by system components.  For example, your code-level traces, your hidden API calls, DB queries, messages, memory bottlenecks, diff coverage, errors, etc.

No. Our code instrumentation is in memory and is not added to the source code. Therefore it does not affect staging or production.

We currently support VSCode. We’ll support additional editors shortly. If you’re not using VSCode, we’ve recently rolled out Sprkl for the web.

Sprkl is available as a VSCode extension/ as a web app (based on Grafana & jaeger) or as a GitHub App for your CI/CD. Follow our docs for getting started instructions.

Sprkl is available on the VSCode marketplace. Here‘s the link.

No. Our code instrumentation is in memory and is not added to the source code. Therefore it does not affect staging or production.

No. Sprkl doesn’t change your code functionality or files.

We don’t change your code’s functionality in any way. Instead, we add an instrumentation layer to your code that only runs on your local machine. We use our intelligent instrumentation engine to leverage OpenTelemetry (a typical, trustworthy open-source project) to apply our instrumentation to your code automatically.

Yes! Sprkl works with Kubernetes and provides auto instrumentation with both OpenTelemetry and Sprkl instrumentation for all the services in the cluster. Check out how to use Sprkl for Kubernetes here.

We leverage OpenTelemetry to automatically instrument every code change and analyze it upon execution. Read our docs to learn more.

Sprkl is available on the VSCode marketplace. Here‘s the link.

Got new feature suggestion or want to comment on existing ones? Connect with us: Here

TBA soon – we’re working on it.

No, unless you really want to :). We think it’s TMI and isn’t helpful. We want to help you focus on what matters.

Sprkl for CI (new) enables you to see Sprkl info in CI/CD. We’ll gradually support staging and production environments. We aim to show you how your code changes function throughout the entire lifecycle.

We focus on what you need to see to ship better code faster. Therefore, we focus on what is relevant to your own code change – how it affects and is affected by system components.  For example, your code-level traces, your hidden API calls, DB queries, messages, memory bottlenecks, diff coverage, errors, etc.

No. Our code instrumentation is in memory and is not added to the source code. Therefore it does not affect staging or production.

We currently support VSCode. We’ll support additional editors shortly. If you’re not using VSCode, we’ve recently rolled out Sprkl for the web.

Sprkl is available as a VSCode extension/ as a web app (based on Grafana & jaeger) or as a GitHub App for your CI/CD. Follow our docs for getting started instructions.

By using Sprkl, you immediately understand how your code performs. You no longer need to spend time manually collecting data and trying to piece it all together. No more sifting through endless logs or traces, adding breakpoints, or switching from one tool to another. Sprkl helps you research, plan, debug, test, and prevent issues, and investigate existing issues faster so you can focus on writing your best possible code. 

Sprkl is a Personal Observability platform that provides personalized feedback on your code changes while coding. Sprkl helps ship correct and efficient code while spending less time on debugging, code review, and frustrating rework. Powered by OpenTelemetry, Sprkl instruments every code change and analyzes it upon execution. Watch Sprkl feedback while coding (VSCode/ web / during CI).

Watch a short Sprkl demo here.

Sprkl currently supports Node v16.1.0 or higher. 

Using sprkl with TypeScript is as easy as using it for native Javascript. Just make sure that you enable sourcemaps when building the code, and that the sourcemaps are available when running sprkl (either as files with the compiled code or inlined).
Example using esbuild: esbuild –sourcemap …
Example using tsc (tsconfig.json):

Of course. Sprkl can instrument any git recipe you can think of. For example, you can instrument or exclude: uncommitted changes, my commits only; all commits since I left the main branch; all commits in the last six months, etc. Those are configurable.

No. It comes out of the box: you don’t need to deal with the hassle of installing it.

We instrument your code change alone, instead of your entire codebase. The instrumentation will only be applied to the specific part of your code that you want to instrument, not to your whole codebase and will not affect staging or production modes. 

No. Sprkl doesn’t change your code functionality or files.

We don’t change your code’s functionality in any way. Instead, we add an instrumentation layer to your code that only runs on your local machine. We use our intelligent instrumentation engine to leverage OpenTelemetry (a typical, trustworthy open-source project) to apply our instrumentation to your code automatically.

Node.js v16.10 and up (Java, C#, and Python are partially supported via our Kubernetes Setup). We gradually adding support for additional languages. Please tell us what you’d like us to support:Here.

Yes! Read more here.

The Sprkl Operator is an improvement of the OpenTelemetry Operator. The OpenTelemetry Operator applies automatic library and infrastructure-level instrumentation. The Sprkl Operator provides the same functionality and integrates Sprkl instrumentation with it. Together Sprkl brings you cluster-level distributed tracing with personalization on your Node.js services. Read more on our docs.

We leverage OpenTelemetry to automatically instrument every code change and analyze it upon execution. Read our docs to learn more.

We instrument your code change alone, instead of your entire codebase. The instrumentation will only be applied to the specific part of your code that you want to instrument, not to your whole codebase and will not affect staging or production modes. 

No. Our code instrumentation is in memory and is not added to the source code. Therefore it does not affect staging or production.

Yes! Sprkl ships with Jest testing instrumentation (unit and integration tests), providing insights and traces for every execution. You can get an overview of the execution of your tests, including details for mocks and assertions. Get a better understanding of what is tested (or not tested) for the code changes you analyze. Read more here or this article in our blog.

Yes! Sprkl works with Kubernetes and provides auto instrumentation with both OpenTelemetry and Sprkl instrumentation for all the services in the cluster. Check out how to use Sprkl for Kubernetes here.

Sprkl for CI (new) enables you to see Sprkl info in CI/CD. We’ll gradually support staging and production environments. We aim to show you how your code changes function throughout the entire lifecycle.

No. Sprkl doesn’t change your code functionality or files.

We don’t change your code’s functionality in any way. Instead, we add an instrumentation layer to your code that only runs on your local machine. We use our intelligent instrumentation engine to leverage OpenTelemetry (a typical, trustworthy open-source project) to apply our instrumentation to your code automatically.

Got new feature suggestion or want to comment on existing ones? Connect with us: Here

Yes – Sprkl is free. However, we’d appreciate it if you spread the word amongst your fellow devs and communities that you engage in.

Yes! Sprkl ships with Jest testing instrumentation (unit and integration tests), providing insights and traces for every execution. You can get an overview of the execution of your tests, including details for mocks and assertions. Get a better understanding of what is tested (or not tested) for the code changes you analyze. Read more here or this article in our blog.

Yes! Sprkl works with Kubernetes and provides auto instrumentation with both OpenTelemetry and Sprkl instrumentation for all the services in the cluster. Check out how to use Sprkl for Kubernetes here.

Using sprkl with TypeScript is as easy as using it for native Javascript. Just make sure that you enable sourcemaps when building the code, and that the sourcemaps are available when running sprkl (either as files with the compiled code or inlined).
Example using esbuild: esbuild –sourcemap …
Example using tsc (tsconfig.json):

No. It comes out of the box: you don’t need to deal with the hassle of installing it.

Sprkl is available as a VSCode extension/ as a web app (based on Grafana & jaeger) or as a GitHub App for your CI/CD. Follow our docs for getting started instructions.

The Sprkl Operator is an improvement of the OpenTelemetry Operator. The OpenTelemetry Operator applies automatic library and infrastructure-level instrumentation. The Sprkl Operator provides the same functionality and integrates Sprkl instrumentation with it. Together Sprkl brings you cluster-level distributed tracing with personalization on your Node.js services. Read more on our docs.

Sprkl currently supports Node v16.1.0 or higher. 

No, unless you really want to :). We think it’s TMI and isn’t helpful. We want to help you focus on what matters.

Sprkl for CI (new) enables you to see Sprkl info in CI/CD. We’ll gradually support staging and production environments. We aim to show you how your code changes function throughout the entire lifecycle.