Frontend Error Capture
A 2-step recipe with Highlight (highlight.io). We can help you get access.
Recipe · 2 steps
Frontend Error Capture
Open a session and push frontend errors to Highlight for grouping.
- Run the initializeSession GraphQL mutation to open a session, then branch on whether a secure id was returned.
- Run the pushPayload GraphQL mutation with the frontend errors array attached to the session so Highlight aggregates them into error groups.
What you'll need to have ready
- organizationVerboseId: The Highlight project verbose id that owns the session.
- clientVersion: The highlight.run client SDK version.
- firstloadVersion: The firstload script version.
- environment: The deployment environment the errors were captured in.
- clientId: A stable client identifier for the browser.
- errors: The array of frontend ErrorObjectInput records to report.
- messages: Serialized console/network messages accompanying the errors.
- events: The rrweb events object for the payload (may be empty).
For your developer
Arazzo workflow highlight-io:frontend-error-capture, 2 operations: executePublicGraphMutation → executePublicGraphMutation. Specs on APIs.io.