OpenTelemetry

Description

You can send your logs, metrics and traces to any destination that accepts data using the OpenTelemetry protocol, for example Grafana, TelemetryHub, or New Relic.

Data Type Compatibility

This table shows data type compatibility across Sources and Destinations within OpenTelemetry context.

Source Data Type		Destination Data Type	Compatibility
OpenTelemetry - Log	➔	OpenTelemetry - Log	✅
Any Source - Log	➔	OpenTelemetry - Log	❌
Any Source - Metric	➔	OpenTelemetry - Metric	✅
OpenTelemetry - Trace	➔	OpenTelemetry - Trace	✅
Any Source - Trace	➔	OpenTelemetry - Trace	❌

Configuration

You can configure the Destination using these options.

Configuration Options

Option	Description
Collector Endpoint	The OpenTelemetry Collector URL that receives the data. Only HTTP protocol is supported. No paths `/v1/logs` `/v1/metrics` `/v1/traces` needed, they will be added automatically based on a data type detected by the Destination.
End-to-end acknowledgement	Enable this option to receive verification that OpenTelemetry data is being received by OTLP collector.
Strategy	The authentication strategy to use.
HTTP Headers	Additional headers to be sent with a request. The most common case is to set a secret key to authorize a request. Note: Authorization header is prohibited in case if some strategy has been already set up.
Compression	Compression option: `none` or `gzip` to reduce network traffic

About Pipelines

Sources

Processors

Destinations

Pipeline Management

Other Topics

Description

Data Type Compatibility

Configuration

Configuration Options

​Description

​Data Type Compatibility

​Configuration

​Configuration Options

Description

Data Type Compatibility

Configuration

Configuration Options