Backend Error Report
A 2-step recipe with Highlight (highlight.io). We can help you get access.
Recipe · 2 steps
Backend Error Report
with Highlight (highlight.io) · Observability Management
Report a backend error to Highlight as a correlated OTLP error span and error log.
- Submit an OTLP span with STATUS_CODE_ERROR status and an exception event that captures the error type, message, and stacktrace.
- Submit an OTLP ERROR-severity log record for the same project and trace id so the error message is searchable and grouped alongside the error span.
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 error log.
- spanId: 8-byte span identifier encoded as hex.
- spanName: Name of the span in which the error occurred.
- startTimeUnixNano: Span start time in nanoseconds since the UNIX epoch.
- endTimeUnixNano: Span end time in nanoseconds since the UNIX epoch.
- errorType: The exception type used as the exception.type span event attribute.
- errorMessage: The error message, reused as exception.message and the log body.
- errorStacktrace: The exception stacktrace recorded as the exception.stacktrace span event attribute.
- errorTimeUnixNano: Timestamp of the error log record in nanoseconds since the UNIX epoch.
For your developer
Arazzo workflow highlight-io:backend-error-report, 2 operations: exportTraces → exportLogs. Specs on APIs.io.