Skip to content

Error Reporting ​

Use Administration → Services → Error Reporting to manage shared reporting profiles for Sentry or GlitchTip. Platform Admin configures profiles and assigns them to services.

Create and assign a profile ​

Create a profile with a name, the destination project's DSN, and an optional environment such as production. Enable the profile, then select it when editing the service that should report errors. A profile can serve several services; use separate profiles when they need different destinations or environments.

Profiles are available for Edge, Cache, Net, Relay, Runners, SNMP, Telematik, Webhooks, Intel AMT and Package Discovery. Endpoint agents and Microsoft 365 clients are outside this feature.

Choose the backend and frontend profiles independently under Administration → Settings → Error Reporting. Frontend reporting starts when the user next fully loads the page, including the sign-in page.

Change or disable reporting ​

Reporting is disabled until an enabled profile is assigned. Select None to disable one service, or disable a shared profile to stop reporting for all its assignments. Reassign services before deleting a profile they use.

Connected services apply profile changes automatically. A disconnected service keeps its last received configuration until it reconnects. Backend changes apply to subsequent errors; frontend changes apply on the next full page load.

Reported information ​

Reports cover unexpected application errors and include stack traces, the service identity, release version and configured environment. Expected operational failures, such as an unreachable device, a rejected request or a cancelled job, remain in their usual Ordyn results and logs.

Error reports are sent to the assigned destination with sensitive fields scrubbed. Performance tracing, request bodies and user identity are not collected for this feature. A reporting destination becoming unavailable does not stop the service's work.