Correlated Backend Telemetry Export
A 3-step recipe with Highlight (highlight.io). We can help you get access.
Recipe · 3 steps
Correlated Backend Telemetry Export
with Highlight (highlight.io) · Observability Management
Emit a correlated OTLP trace, logs, and metrics batch for one Highlight project.
- Submit a single OTLP span carrying the highlight.project_id resource attribute and the supplied trace and span identifiers.
- Submit OTLP log records for the same project that reference the trace id from the span so the logs correlate to it in Highlight.
- Submit an OTLP gauge data point for the same project, completing the correlated trace, logs, and metrics slice.
What you'll need to have ready
- projectId: The Highlight project verbose id used as the highlight.project_id resource attribute.
- serviceName: The emitting service name (service.name resource attribute).
- traceId: 16-byte trace identifier encoded as hex, shared by the span and the logs.
- spanId: 8-byte span identifier encoded as hex.
- spanName: Human-readable name of the span.
- startTimeUnixNano: Span start time in nanoseconds since the UNIX epoch.
- endTimeUnixNano: Span end time in nanoseconds since the UNIX epoch.
- logTimeUnixNano: Timestamp of the log record in nanoseconds since the UNIX epoch.
- logSeverityText: Human-readable severity for the log record.
- logBody: The log message body.
- metricName: The OTLP metric name.
- metricTimeUnixNano: Timestamp of the metric data point in nanoseconds since the UNIX epoch.
For your developer
Arazzo workflow highlight-io:correlated-backend-telemetry-export, 3 operations: exportTraces → exportLogs → exportMetrics. Specs on APIs.io.