capabilities.work

Fullstack Error Correlation

A 3-step recipe with Highlight (highlight.io). We can help you get access.

Recipe · 3 steps

Fullstack Error Correlation

with Highlight (highlight.io)

Open a session, then report frontend and backend errors keyed to it.

  1. Run the initializeSession GraphQL mutation to open a session and return its session_secure_id for use as the correlation key.
  2. Run the pushPayload GraphQL mutation to report the frontend error against the session.
  3. Run the pushBackendPayload GraphQL mutation to report the backend error for the same project, correlating it to the session.
What you'll need to have ready
  • organizationVerboseId: The Highlight project verbose id used to open the session.
  • projectVerboseId: The Highlight project verbose id used for the backend payload.
  • clientVersion: The highlight.run client SDK version.
  • firstloadVersion: The firstload script version.
  • environment: The deployment environment.
  • clientId: A stable client identifier for the browser.
  • frontendErrors: The array of frontend ErrorObjectInput records.
  • backendErrors: The array of backend BackendErrorObjectInput records.
For your developer

Arazzo workflow highlight-io:fullstack-error-correlation, 3 operations: executePublicGraphMutation → executePublicGraphMutation → executePublicGraphMutation. Specs on APIs.io.

More recipes with Highlight (highlight.io)

Backend Error ReportBackend Session PayloadBrowser Session LifecycleCorrelated Backend Telemetry ExportFrontend Error CaptureFullstack Session CorrelationLogs and Metrics BatchSession Feedback CaptureSession Track Event