Retire events nothing consumes, along with the dashboards reading them
Events emitted for a dashboard nobody opens, removed on consumption evidence.
The ticket
Remove events that nothing consumes, along with their unused dashboards.
Acceptance criteria
- Consumption evidence covering a full quarter is attached
- Dashboards and alerts reading them are checked, not only queries
- Events are deprecated before removal, with a stated window
- Payload size reduction is recorded
What lands as proof
Consumption evidence over a quarter, so removal is based on data rather than on nobody objecting.
Why teams defer it
- Somebody may be querying it ad hoc, and proving otherwise takes a quarter of evidence.
- Events are cheap individually, so the accumulated payload cost never gets attributed to any one of them.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: remove events that nothing consumes, along with their unused dashboards. 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 consumption evidence attached before removal, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- The run stops for the plan, and the review bar is raised afterwards so that smaller suggestions block the merge too, not only serious findings.