Fullstack Session Correlation
A 2-step recipe with Highlight (highlight.io). We can help you get access.
Recipe · 2 steps
Fullstack Session Correlation
with Highlight (highlight.io) · Observability Management
Open a Highlight session and emit a backend span tagged with its session id.
- Run the initializeSession GraphQL mutation to open a session and return its session_secure_id for use as the backend correlation key.
- Submit an OTLP span carrying highlight.session_id set to the session secure id so the backend trace correlates with the frontend replay.
What you'll need to have ready
- organizationVerboseId: The Highlight project verbose id used when opening the session.
- projectId: The Highlight project verbose id used as the highlight.project_id resource attribute on the span.
- clientVersion: The highlight.run client SDK version.
- firstloadVersion: The firstload script version.
- environment: The deployment environment.
- clientId: A stable client identifier for the browser.
- serviceName: The emitting backend service name.
- traceId: 16-byte trace identifier encoded as hex.
- spanId: 8-byte span identifier encoded as hex.
- spanName: Name of the backend span.
- startTimeUnixNano: Span start time in nanoseconds since the UNIX epoch.
- endTimeUnixNano: Span end time in nanoseconds since the UNIX epoch.
For your developer
Arazzo workflow highlight-io:fullstack-session-correlation, 2 operations: executePublicGraphMutation → exportTraces. Specs on APIs.io.