Sentry Monitoring

Last reviewed: 2026-05-13
Maintained by: Engineering

Sentry is wired as an optional, environment-controlled monitoring layer across the API and client apps.

Current behavior

• startup must not fail when Sentry is disabled or a DSN is missing
• local development should keep Sentry disabled unless a developer is intentionally testing it
• runtime release, environment, and trace sampling values come from environment variables

Current integration points

• API: apps/api/src/lib/sentry.ts
• Manager Desk: apps/manager-desk/lib/sentry.ts
• Back Office: apps/back-office/lib/sentry.ts
• Mobile: apps/zgrid-mobile/src/lib/sentry.ts

Important implementation notes

• API error handling captures 5xx failures and includes request correlation data
• sensitive request fields are sanitized before events are sent
• browser and mobile setup are opt-in through public environment flags and DSNs

See also:

• ../99-reference/environment-contract.md
• ../04-operations/infrastructure.md