Skip to Content
UDS Simulator 2.0 Released

Docs baseline actions

Copy this page URLEdit page
DocsMonitoring & Error Reporting

Monitoring & Error Reporting

The simulator uses Sentry to capture unhandled frontend errors. Event sending is gated by analytics consent and only activates when a DSN is configured.

Configuration

  1. Add VITE_SENTRY_DSN to your environment variables.
  2. (Optional) Set VITE_SENTRY_TRACES_SAMPLE_RATE to enable performance tracing.
  3. Deploy the frontend with the DSN set.
tip _entry

Events are only sent when analytics consent is granted. If consent is revoked, events are dropped.

Privacy Notes

  • Default PII is disabled.
  • Error reporting does not start without a DSN.
  • Tracing only starts when VITE_SENTRY_TRACES_SAMPLE_RATE is greater than 0.
  • Error and tracing events are both blocked when analytics consent is disabled.

Validation Checklist

  • Trigger a test error in development and confirm it appears in Sentry.
  • Verify no events are sent before granting analytics consent.
  • With tracing enabled, navigate between pages and confirm transactions appear in Sentry.