Problem: Error tracking and tracing (src/selfhost/sentry.ts) today only activate if an operator sets their own SENTRY_DSN — zero central visibility by default, appropriate for self-host but not for a centrally-hosted fleet gittensory itself operates.
Area: ORB / Incident readiness.
Proposal: Stand up centrally-owned observability for the hosted fleet specifically — gittensory's own Sentry (or equivalent) project, wired into the hosted control-plane and tenant containers — distinct from and not replacing each self-host operator's own opt-in stack (src/selfhost/sentry.ts stays exactly as-is for self-host).
Deliverables:
Resources
src/selfhost/sentry.ts (the existing per-operator opt-in pattern — do not modify; this is additive, hosted-only)
maintainer-only — requires a real, live third-party account/dashboard setup (a new Sentry project, DSN provisioning) that a contributor structurally can't have access to; this is a maintainer-executed ops task, not a GitHub-issue-shaped code change on its own (though wiring the repo-side code to point at whatever DSN the maintainer provisions could be split out separately once the account exists).
Problem: Error tracking and tracing (
src/selfhost/sentry.ts) today only activate if an operator sets their ownSENTRY_DSN— zero central visibility by default, appropriate for self-host but not for a centrally-hosted fleet gittensory itself operates.Area: ORB / Incident readiness.
Proposal: Stand up centrally-owned observability for the hosted fleet specifically — gittensory's own Sentry (or equivalent) project, wired into the hosted control-plane and tenant containers — distinct from and not replacing each self-host operator's own opt-in stack (
src/selfhost/sentry.tsstays exactly as-is for self-host).Deliverables:
Resources
src/selfhost/sentry.ts(the existing per-operator opt-in pattern — do not modify; this is additive, hosted-only)maintainer-only — requires a real, live third-party account/dashboard setup (a new Sentry project, DSN provisioning) that a contributor structurally can't have access to; this is a maintainer-executed ops task, not a GitHub-issue-shaped code change on its own (though wiring the repo-side code to point at whatever DSN the maintainer provisions could be split out separately once the account exists).