Problem
Split from #4934. Part of epic #8286 (Phase 1 — Errors). Once a loopover-owned PostHog project exists (#7875), the hosted control-plane and tenant containers need to actually report to it — today nothing does (self-host's src/selfhost/sentry.ts only reports for an operator who sets their own SENTRY_DSN; the hosted fleet itself has no central error visibility at all).
Originally scoped for a central Sentry DSN; reworked for PostHog per the project's Sentry→PostHog migration (epic #8286) — same shape of task (consume an already-provisioned key, wire it into the hosted path), different vendor.
Area
control-plane/, hosted container entry points (ORB hosted Worker, AMS tenant containers).
Proposal
Wire the hosted control-plane and tenant containers to report to the central PostHog project, reusing whatever init pattern each Phase-1 sub-issue establishes for its surface (self-host server pattern for Node-based hosted pieces, Worker raw-capture pattern for the hosted ORB Worker) rather than inventing a third mechanism. The project key itself is injected as a control-plane secret (per #7875's own deliverable), never hardcoded or committed.
Deliverables
Resources
Boundaries
Wiring only — does not provision the PostHog project itself (#7875, separate).
Contributor-eligible once #7875 lands (a real key to point at) and at least one Phase-1 sub-issue has established the init pattern to reuse. No new integration mechanism invented.
Problem
Split from #4934. Part of epic #8286 (Phase 1 — Errors). Once a loopover-owned PostHog project exists (#7875), the hosted control-plane and tenant containers need to actually report to it — today nothing does (self-host's
src/selfhost/sentry.tsonly reports for an operator who sets their ownSENTRY_DSN; the hosted fleet itself has no central error visibility at all).Originally scoped for a central Sentry DSN; reworked for PostHog per the project's Sentry→PostHog migration (epic #8286) — same shape of task (consume an already-provisioned key, wire it into the hosted path), different vendor.
Area
control-plane/, hosted container entry points (ORB hosted Worker, AMS tenant containers).Proposal
Wire the hosted control-plane and tenant containers to report to the central PostHog project, reusing whatever init pattern each Phase-1 sub-issue establishes for its surface (self-host server pattern for Node-based hosted pieces, Worker raw-capture pattern for the hosted ORB Worker) rather than inventing a third mechanism. The project key itself is injected as a control-plane secret (per #7875's own deliverable), never hardcoded or committed.
Deliverables
Resources
Boundaries
Wiring only — does not provision the PostHog project itself (#7875, separate).
Contributor-eligible once #7875 lands (a real key to point at) and at least one Phase-1 sub-issue has established the init pattern to reuse. No new integration mechanism invented.