Replace an analytics or logging vendor, call site by call site
A vendor swap done call site by call site, with event parity proven rather than assumed.
The ticket
Migrate call sites from one analytics or logging vendor to another, preserving event parity.
Acceptance criteria
- Each migrated call site emits an equivalent event to the new vendor
- A parity test compares old and new payloads
- Both run side by side until parity is confirmed
- The old integration is removed once parity holds
What lands as proof
A parity comparison between the two emitters, which stops a dashboard quietly losing a metric.
Why teams defer it
- Dashboards and alerts depend on the old events, so a gap is only noticed when somebody opens a report.
- Running both vendors at once costs money, which puts a clock on the migration.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: migrate call sites from one analytics or logging vendor to another, preserving event parity. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means event parity test between the old and the new emitter, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- The run stops once the plan is written. Somebody reads the approach and approves it before any code exists, which is the cheapest moment to redirect the work.