@opentelemetry/exporter-zipkin
Advanced tools
OpenTelemetry Zipkin Exporter allows the user to send collected traces to Zipkin.
The @opentelemetry/exporter-zipkin package is designed for Node.js and web applications to export telemetry data to Zipkin, a distributed tracing system. It allows developers to monitor and troubleshoot their applications by collecting and reporting timing data needed to troubleshoot latency problems in microservice architectures. This package is part of the OpenTelemetry project, which provides a set of APIs, libraries, agents, and instrumentation to create and manage telemetry data (metrics, logs, and traces).
Exporting Traces to Zipkin
This code snippet demonstrates how to set up the ZipkinExporter with the OpenTelemetry Node.js SDK. It initializes a NodeTracerProvider, configures the ZipkinExporter with the service name and Zipkin server URL, and registers the exporter using a SimpleSpanProcessor.
{
const { ZipkinExporter } = require('@opentelemetry/exporter-zipkin');
const { SimpleSpanProcessor } = require('@opentelemetry/tracing');
const { NodeTracerProvider } = require('@opentelemetry/node');
const provider = new NodeTracerProvider();
const zipkinExporter = new ZipkinExporter({
serviceName: 'your-service-name',
url: 'http://localhost:9411/api/v2/spans'
});
provider.addSpanProcessor(new SimpleSpanProcessor(zipkinExporter));
provider.register();
}Similar to the Zipkin exporter, the Jaeger exporter allows exporting traces to Jaeger, another open-source, end-to-end distributed tracing system. It provides functionality to send telemetry data to a Jaeger backend, facilitating the monitoring and troubleshooting of microservices-based distributed systems. The choice between Zipkin and Jaeger often depends on the specific needs of the project and the existing infrastructure.
While not directly similar in terms of exporting traces, the Prometheus exporter is another telemetry data exporter that focuses on metrics. It allows exporting metrics data to a Prometheus monitoring system. This package is useful for users who are looking to monitor their application's performance and health through metrics rather than tracing data. It complements the functionality provided by the Zipkin exporter by offering a different aspect of telemetry data monitoring.
OpenTelemetry Zipkin Trace Exporter allows the user to send collected traces to Zipkin.
Zipkin is a distributed tracing system. It helps gather timing data needed to troubleshoot latency problems in microservice architectures. It manages both the collection and lookup of this data.
npm install --save @opentelemetry/exporter-zipkin
Install the exporter on your application and pass the options. serviceName is an optional string. If omitted, the exporter will first try to get the service name from the Resource. If no service name can be detected on the Resource, a fallback name of "OpenTelemetry Service" will be used.
const { ZipkinExporter } = require('@opentelemetry/exporter-zipkin');
// Add your zipkin url (`http://localhost:9411/api/v2/spans` is used as
// default) and application name to the Zipkin options.
// You can also define your custom headers which will be added automatically.
const options = {
headers: {
'my-header': 'header-value',
},
url: 'your-zipkin-url',
serviceName: 'your-application-name',
// optional interceptor
getExportRequestHeaders: () => {
return {
'my-header': 'header-value',
}
}
}
const exporter = new ZipkinExporter(options);
Now, register the exporter and start tracing.
tracer.addSpanProcessor(new BatchSpanProcessor(exporter));
You can use built-in SimpleSpanProcessor or BatchSpanProcessor or write your own.
SpanProcessor that passes ended span directly to the configured SpanExporter.SpanProcessor that batches ended spans and pushes them to the configured SpanExporter. It is recommended to use this SpanProcessor for better performance and optimization.Please visit the Zipkin UI endpoint http://localhost:9411
Apache 2.0 - See LICENSE for more information.
0.20.0
opentelemetry-sdk-node, opentelemetry-tracing
opentelemetry-node, opentelemetry-propagator-jaeger, opentelemetry-shim-opentracing
opentelemetry-core, opentelemetry-instrumentation-grpc, opentelemetry-shim-opentracing, opentelemetry-tracing
opentelemetry-shim-opentracing
opentelemetry-tracing
opentelemetry-core, opentelemetry-exporter-collector-grpc, opentelemetry-exporter-collector-proto, opentelemetry-exporter-collector, opentelemetry-exporter-jaeger, opentelemetry-exporter-zipkin, opentelemetry-metrics, opentelemetry-resources, opentelemetry-sdk-node, opentelemetry-tracing
opentelemetry-api-metrics, opentelemetry-context-async-hooks, opentelemetry-context-zone-peer-dep, opentelemetry-context-zone, opentelemetry-core, opentelemetry-exporter-collector-grpc, opentelemetry-exporter-collector-proto, opentelemetry-exporter-collector, opentelemetry-exporter-jaeger, opentelemetry-exporter-prometheus, opentelemetry-exporter-zipkin, opentelemetry-instrumentation-fetch, opentelemetry-instrumentation-grpc, opentelemetry-instrumentation-http, opentelemetry-instrumentation-xml-http-request, opentelemetry-instrumentation, opentelemetry-metrics, opentelemetry-node, opentelemetry-propagator-b3, opentelemetry-propagator-jaeger, opentelemetry-resource-detector-aws, opentelemetry-resource-detector-gcp, opentelemetry-resources, opentelemetry-sdk-node, opentelemetry-shim-opentracing, opentelemetry-tracing, opentelemetry-web
opentelemetry-instrumentation
opentelemetry-core, opentelemetry-instrumentation-http, opentelemetry-propagator-b3, opentelemetry-propagator-jaeger, opentelemetry-tracing
opentelemetry-core, opentelemetry-tracing
opentelemetry-core, opentelemetry-exporter-collector-grpc, opentelemetry-exporter-collector-proto, opentelemetry-exporter-collector
opentelemetry-exporter-collector, opentelemetry-exporter-zipkin, opentelemetry-tracing
opentelemetry-exporter-collector-grpc
opentelemetry-semantic-conventions
opentelemetry-instrumentation-xml-http-request
opentelemetry-exporter-prometheus
opentelemetry-api-metrics, opentelemetry-exporter-collector-grpc, opentelemetry-exporter-collector-proto, opentelemetry-exporter-collector, opentelemetry-metrics
opentelemetry-exporter-collector-grpc
opentelemetry-tracing
opentelemetry-instrumentation-grpc
opentelemetry-core
opentelemetry-node
opentelemetry-instrumentation-fetch, opentelemetry-instrumentation-grpc, opentelemetry-instrumentation-http, opentelemetry-instrumentation-xml-http-request, opentelemetry-instrumentation, opentelemetry-node, opentelemetry-sdk-node, opentelemetry-web
opentelemetry-api-metrics, opentelemetry-context-async-hooks, opentelemetry-context-zone-peer-dep, opentelemetry-context-zone, opentelemetry-core, opentelemetry-exporter-collector-grpc, opentelemetry-exporter-collector-proto, opentelemetry-exporter-collector, opentelemetry-exporter-jaeger, opentelemetry-exporter-prometheus, opentelemetry-exporter-zipkin, opentelemetry-instrumentation-fetch, opentelemetry-instrumentation-grpc, opentelemetry-instrumentation-http, opentelemetry-instrumentation-xml-http-request, opentelemetry-instrumentation, opentelemetry-metrics, opentelemetry-node, opentelemetry-propagator-b3, opentelemetry-propagator-jaeger, opentelemetry-resource-detector-aws, opentelemetry-resource-detector-gcp, opentelemetry-resources, opentelemetry-sdk-node, opentelemetry-semantic-conventions, opentelemetry-shim-opentracing, opentelemetry-tracing, opentelemetry-web, template
opentelemetry-instrumentation-http, opentelemetry-instrumentation, opentelemetry-tracing
opentelemetry-node, opentelemetry-sdk-node, opentelemetry-web
opentelemetry-api-metrics, opentelemetry-context-zone-peer-dep, opentelemetry-context-zone, opentelemetry-core, opentelemetry-exporter-collector, opentelemetry-exporter-zipkin, opentelemetry-instrumentation-fetch, opentelemetry-instrumentation-xml-http-request, opentelemetry-instrumentation, opentelemetry-propagator-jaeger, opentelemetry-tracing, opentelemetry-web
opentelemetry-sdk-node
opentelemetry-core
opentelemetry-api-metrics, opentelemetry-context-zone-peer-dep, opentelemetry-context-zone, opentelemetry-core, opentelemetry-exporter-collector, opentelemetry-exporter-zipkin, opentelemetry-instrumentation-fetch, opentelemetry-instrumentation-xml-http-request, opentelemetry-instrumentation, opentelemetry-metrics, opentelemetry-propagator-b3, opentelemetry-propagator-jaeger, opentelemetry-resources, opentelemetry-semantic-conventions, opentelemetry-tracing, opentelemetry-web, template
FAQs
OpenTelemetry Zipkin Exporter allows the user to send collected traces to Zipkin.
The npm package @opentelemetry/exporter-zipkin receives a total of 2,434,746 weekly downloads. As such, @opentelemetry/exporter-zipkin popularity was classified as popular.
We found that @opentelemetry/exporter-zipkin demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Fluent Assertions is facing backlash after dropping the Apache license for a commercial model, leaving users blindsided and questioning contributor rights.
Research
Security News
Socket researchers uncover the risks of a malicious Python package targeting Discord developers.
Security News
The UK is proposing a bold ban on ransomware payments by public entities to disrupt cybercrime, protect critical services, and lead global cybersecurity efforts.