opentracing-javascript VS opentelemetry-js

Spring Spring web framework Spring WebFlux Reactive REST Services Spring Data R2DBC a specification to integrate SQL databases using reactive drivers Redisson Redis Java Client Zipkin open source, end-to-end distributed tracing Spring Cloud Sleuth auto-configuration for distributed tracing Prometheus monitoring and alerting Grafana for to compose observability dashboards with everything from Prometheus Kubernetes automating deployment, scaling, and management of containerized applications Docker and docker-compose Helm The package manager for Kubernetes Flywaydb for migrations

Elasticsearch client for Go RabbitMQ Go RabbitMQ Client Library Jaeger open source, end-to-end distributed tracing Prometheus monitoring and alerting Grafana for to compose observability dashboards with everything from Prometheus Echo web framework Kibana is user interface that lets you visualize your Elasticsearch Docker and docker-compose Kubernetes K8s Helm The package manager for Kubernetes

PostgeSQL as event store database Kafka as messages broker gRPC Go implementation of gRPC Jaeger open source, end-to-end distributed tracing Prometheus monitoring and alerting Grafana for to compose observability dashboards with everything from Prometheus MongoDB MongoDB database Elasticsearch Elasticsearch client for Go. Echo web framework Kibana Kibana is data visualization dashboard software for Elasticsearch Migrate for migrations

OpenTracing was an open-source project aimed at providing vendor-neutral APIs and instrumentation for distributed tracing. In distributed cloud-native applications, it is difficult for engineering teams to see how requests are performing across services. And that’s where distributed tracing comes into the picture.

OpenTracing is now archived, and it is suggested to migrate to OpenTelemetry.

In this article let's try to create closer to real world Event Sourcing CQRS microservice using: 🚀👨‍💻🙌 EventStoreDB The database built for Event Sourcing gRPC Go implementation of gRPC MongoDB Web and API based SMTP testing Elasticsearch Elasticsearch client for Go. Jaeger open source, end-to-end distributed tracing Prometheus monitoring and alerting Grafana for to compose observability dashboards with everything from Prometheus swag Swagger for Go Echo web framework Kibana Kibana is user interface that lets you visualize your Elasticsearch

Service mesh - ssup2ket services run on service mesh for detailed traffic control and easy monitoring. Service mesh is applied through Istio. Istio uses OpenTracing for easy request tracing between multiple services.

An OpenTelemetry SDK is a library that runs in your application. It collects traces, metrics, and logs from your code and hands them off for export. You install it, configure it, and call its APIs (or rely on auto-instrumentation) to emit telemetry. For Python agents, the OpenTelemetry Python SDK is the foundation. For TypeScript, OpenTelemetry JavaScript serves the same purpose.

You can't improve what you don't measure: track passkey adoption, auth success rates, and error rates using OpenTelemetry, the industry-standard observability framework. Key metrics to track include: passkey registration rate (percent of users with at least one passkey), passkey auth success rate (percent of passkey logins that succeed), fallback auth rate (percent of logins using TOTP/SMS), and device type breakdown (iOS, Android, Desktop). In our case study, the team noticed that 12% of Android users were falling back to TOTP, which traced to a bug in the WebAuthn implementation for Chrome on Android 11. Without metrics, this issue would have gone unnoticed for months. Use the OpenTelemetry JS library to emit metrics from both client and server. Below is a minimal metric for tracking passkey registrations:

Citations: [1] https://pplx-res.cloudinary.com/image/upload/v1747427714/user_uploads/48031643/6b29f8b1-fff0-45bb-9ae7-f0bc2d98c3cb/17474277015804148959788849369994.jpg [2] https://docs.camunda.io/docs/components/modeler/desktop-modeler/telemetry/ [3] https://camunda.com/blog/2025/02/one-exporter-to-rule-them-all-exploring-camunda-exporter/ [4] https://camunda.com/blog/2025/01/performance-tuning-camunda-8/ [5] https://forum.camunda.io/t/instrumentation-of-camunda-processes-for-open-telemetry/51400 [6] https://docs.camunda.io/docs/self-managed/zeebe-deployment/zeebe-gateway/interceptors/ [7] https://docs.dapr.io/operations/observability/tracing/otel-collector/open-telemetry-collector/ [8] https://docs.camunda.io/docs/8.7/self-managed/operational-guides/monitoring/metrics/ [9] https://camunda.com/blog/2024/04/camunda-8-5-release/ [10] https://github.com/camunda/zeebe/issues/9742 [11] https://www.linkedin.com/pulse/how-implement-custom-interceptors-camunda-85-anubhav-mangla-fl14c [12] https://forum.camunda.io/t/zeebe-and-distributed-tracing/36723 [13] https://javadoc.io/static/io.quarkiverse.zeebe/quarkus-zeebe/0.4.0/io/quarkiverse/zeebe/runtime/tracing/ZeebeOpenTelemetryClientInterceptor.html [14] https://www.linkedin.com/pulse/distributed-tracing-springboot-opentelemetry-api-calls-chandan-khatri-wpw7c [15] https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/12122 [16] https://camunda.com/blog/2022/11/how-to-build-camunda-platform-8-connector/ [17] https://github.com/open-telemetry/opentelemetry-js/issues/2786 [18] https://grafana.com/docs/grafana-cloud/monitor-applications/frontend-observability/instrument/opentelemetry-js/ [19] https://coralogix.com/guides/opentelemetry/opentelemetry-tracing-how-it-works-tutorial-and-best-practices/ [20] https://grafana.com/docs/grafana-cloud/send-data/metrics/metrics-prometheus/prometheus-config-examples/camunda-zeebe/ [21] https://opentelemetry.io/docs/specs/otel/trace/api/

... //https://www.honeycomb.io/blog/opentelemetry-browser-instrumentation //https://github.com/open-telemetry/opentelemetry-js/tree/main/experimental/packages/opentelemetry-instrumentation-xml-http-request //https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/plugins/web/opentelemetry-instrumentation-user-interaction //https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/plugins/web/opentelemetry-instrumentation-long-task //https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/plugins/web/opentelemetry-instrumentation-long-task export default async () => { const otlpOptions = { omitted }; const attributes = { omitted } provider.addSpanProcessor(new SimpleSpanProcessor(new OTLPTraceExporter(otlpOptions))); provider.register({contextManager: new StackContextManager()}); registerInstrumentations({ instrumentations: [ getWebAutoInstrumentations({ '@opentelemetry/instrumentation-xml-http-request': { clearTimingResources: true, } }), new LongTaskInstrumentation({ observerCallback: (span, longtaskEvent) => { span.setAttribute('location.pathname', window.location.pathname) } }), new FetchInstrumentation({ propagateTraceHeaderCorsUrls: [new RegExp('\\/api\\/*')], ignoreUrls: [new RegExp('\\/tile\\/*')], })], }); ... };

To enable only @opentelemetry/instrumentation-http and @opentelemetry/instrumentation-express you can run this command below.

JavaScript

> OpenTelemetry is a marketing-driven project, designed by committee, implemented naively and inefficiently, and guided by the primary goal of allowing Fortune X00 CTOs to tick off some boxes on their strategy roadmap documents.

I'm the founder of highlight.io. On the consumer side as a company, we've seen a lot of value of from OTEL; we've used it to build out language support for quite a few customers at this point, and the community is very receptive.

Here's an example of us putting up a change: https://github.com/open-telemetry/opentelemetry-js/pull/4049

Do you mind sharing why you think no-one should be using it? Some reasoning would be nice.

That's traces? I was wondering if I could use https://github.com/open-telemetry/opentelemetry-js/tree/main...

Nothing like Faro for now. However, https://github.com/open-telemetry/opentelemetry-js can be used to achieve the same result and OpenObserve has great support for Opentelemetry.