Note: This is an experimental package under active development. New releases may include breaking changes.
This module provides exporter for node to be used with OTLP (http/protobuf
) compatible receivers.
Compatible with opentelemetry-collector versions >=0.32 <=0.50
.
npm install --save @opentelemetry/exporter-trace-otlp-proto
The OpenTelemetry Collector Exporter does not have a service name configuration.
In order to set the service name, use the service.name
resource attribute as prescribed in the OpenTelemetry Resource Semantic Conventions.
To see documentation and sample code for the metric exporter, see the exporter-metrics-otlp-proto package
const { BasicTracerProvider, SimpleSpanProcessor } = require('@opentelemetry/sdk-trace-base');
const { OTLPTraceExporter } = require('@opentelemetry/exporter-trace-otlp-proto');
const collectorOptions = {
url: '<opentelemetry-collector-url>', // url is optional and can be omitted - default is http://localhost:4318/v1/traces
headers: {
foo: 'bar'
}, //an optional object containing custom headers to be sent with each request will only work with http
};
const provider = new BasicTracerProvider();
const exporter = new OTLPTraceExporter(collectorOptions);
provider.addSpanProcessor(new SimpleSpanProcessor(exporter));
provider.register();
The OTLPTraceExporter has a timeout configuration option which is the maximum time, in milliseconds, the OTLP exporter will wait for each batch export. The default value is 10000ms.
To override the default timeout duration, use the following options:
-
Set with environment variables:
Environment variable Description OTEL_EXPORTER_OTLP_TRACES_TIMEOUT The maximum waiting time, in milliseconds, allowed to send each OTLP trace batch. Default is 10000. OTEL_EXPORTER_OTLP_TIMEOUT The maximum waiting time, in milliseconds, allowed to send each OTLP trace and metric batch. Default is 10000. OTEL_EXPORTER_OTLP_TRACES_TIMEOUT
takes precedence and overridesOTEL_EXPORTER_OTLP_TIMEOUT
. -
Provide
timeoutMillis
to OTLPTraceExporter withcollectorOptions
:const collectorOptions = { timeoutMillis: 15000, url: '<opentelemetry-collector-url>', // url is optional and can be omitted - default is http://localhost:4318/v1/traces headers: { foo: 'bar' }, //an optional object containing custom headers to be sent with each request will only work with http }; const exporter = new OTLPTraceExporter(collectorOptions);
Providing
timeoutMillis
withcollectorOptions
takes precedence and overrides timeout set with environment variables.
OTLP requires that transient errors be handled with a retry strategy.
This retry policy has the following configuration, which there is currently no way to customize.
DEFAULT_EXPORT_MAX_ATTEMPTS
: The maximum number of attempts, including the original request. Defaults to 5.DEFAULT_EXPORT_INITIAL_BACKOFF
: The initial backoff duration. Defaults to 1 second.DEFAULT_EXPORT_MAX_BACKOFF
: The maximum backoff duration. Defaults to 5 seconds.DEFAULT_EXPORT_BACKOFF_MULTIPLIER
: The backoff multiplier. Defaults to 1.5.
This retry policy first checks if the response has a 'Retry-After'
header. If there is a 'Retry-After'
header, the exporter will wait the amount specified in the 'Retry-After'
header before retrying. If there is no 'Retry-After'
header, the exporter will use an exponential backoff with jitter retry strategy.
The exporter will retry exporting within the exporter timeout configuration time.
- Go to examples/otlp-exporter-node
- run
npm run docker:start
- Open page at
http://localhost:9411/zipkin/
to observe the traces
- For more information on OpenTelemetry, visit: https://opentelemetry.io/
- For more about OpenTelemetry JavaScript: https://github.com/open-telemetry/opentelemetry-js
- For help or feedback on this project, join us in GitHub Discussions
Apache 2.0 - See LICENSE for more information.