OpenTelemetry

Already instrumented with OTel? Point your collector at the OTLP endpoint — traces, metrics and logs land in the same places the native collectors write to

Collector configuration

Add this exporter to your OTel Collector and send every pipeline to it. The endpoint and the key are shown in the table below; the key is one of this organization's API keys. Both OTLP/HTTP encodings are accepted — protobuf (the default) and JSON — so there is no line to change.

exporters: otlphttp: endpoint: <OTLP endpoint below> headers: X-API-Key: <your ingest key> service: pipelines: traces:  { exporters: [otlphttp] } metrics: { exporters: [otlphttp] } logs:    { exporters: [otlphttp] }

An SDK exporter works too — setOTEL_EXPORTER_OTLP_ENDPOINTto the same URL andOTEL_EXPORTER_OTLP_HEADERS=X-API-Key=…. The SDK default,http/protobuf, is accepted as-is . Setservice.nameon your resource — it is what every page groups telemetry by.

OTLP ingest

What this organization’s collector has actually delivered, per signal — the onboarding check

SignalEndpointLast receivedRecordsStatus
traces

nothing received yet

otlp/httpnot yet0Not connected

No matching results

LoveHeartBeat - A Product from RootVyana.

v1.24.0

Theme Customizer

Explore different styles according to your preferences

Color Scheme
RTL

Change text direction

Support Chat

Toggle support chat

Navigation Type
Vertical Navbar Appearance
Horizontal Navbar Shape
Horizontal Navbar Appearance
Purchase template
customize