[Observability] Exception Tracking with Sentry (tenant tagging)

[fbenmadani]

Integrate Sentry for exception tracking with tenant context.

Tasks:

• Install Sentry Laravel SDK
• Configure DSN
• Tag all errors with tenant_id

Outcome:
Centralized error tracking per tenant.

[linear]

SF-10

[m13v]

the part that bites with tag-all-errors-with-tenant_id isn't the tagging, it's Sentry's per-event pricing underneath it. your noisiest tenant burns the quota first, so sampling kicks in, and the tenant throwing the most exceptions gets sampled hardest, exactly the one you need full traces for. tenant_id as a tag also still ships every stack trace and request body to Sentry's cloud, so per-tenant isolation is a filter not a boundary. NightOwl's built on the official Laravel Nightwatch package so capture stays laravel-native, keeps data in your own infra on flat pricing so one loud tenant doesn't cost fidelity.