Lumigo OpenTelemetry Endpoint

All you need to know about the way Lumigo ingests OpenTelemetry data

The OpenTelemetry Protocol (otlp) is is a general-purpose telemetry data delivery protocol designed in the scope of the OpenTelemetry project.

Supported transports

  • OTLP/HTTP, using either the protobuf or json endcoding.

Supported subset

Lumigo accepts tracing data, scopes and resource attributes.

Lumigo OpenTelementry Endpoint URL

Lumigo's endpoint to receive OTLP/HTTP data is globally available at:

https://ga-otlp.lumigo-tracer-edge.golumigo.com

📘

Do not append 'v1/traces' to the Lumigo OTLP endpoint URL

In virtually all cases, the OpenTelemetry exporter will append a v1/traces path to the endpoint when exporting tracing data. It is a common configuration mistake to add v1/traces when providing and endpoint URL.

Lumigo OpenTelemetry Authorization

The Lumigo OpenTelemetry Endpoint requires the Authorization HTTP header to be provided by the exporter as follows:

Authorization: LumigoToken <token>

Replace <token> with the token provided in Lumigo on the Settings -> Tracing -> Manual tracing screen.

Lumigo OpenTelemetry Errors

Authorization header is missing

In case you Authorization header is missing, you will receive an HTTP 401 status code with the following message:

The 'Authorization: LumigoToken <token>' header is missing

Authorization header is malformed

In case you Authorization header is malformed, you will receive an HTTP 401 status code with the following message:

The value of the 'Authorization' header is invalid; expected a 'LumigoToken <token>' value

Did this page help you?