Context
version-header.interceptor/deprecation-warning.interceptor emit 299 warnings for v1, but nothing measures how many deprecated requests occur over time.
Problem
The team can't decide rationally when to sunset v1 without traffic data; docs (API_VERSIONING.md) promise a sunset policy that is currently guesswork. A lone signal would prevent breaking active integrations.
Proposed approach
Increment a api_version_requests_total{version} counter (metrics module) in the version interceptor/middleware, expose per-version usage in admin, and track deprecation-warning counts; document the gate criteria for sunset.
Acceptance criteria
- Per-version request metrics exist and are tested; dashboard shows usage.
Context
version-header.interceptor/deprecation-warning.interceptoremit 299 warnings for v1, but nothing measures how many deprecated requests occur over time.Problem
The team can't decide rationally when to sunset v1 without traffic data; docs (
API_VERSIONING.md) promise a sunset policy that is currently guesswork. A lone signal would prevent breaking active integrations.Proposed approach
Increment a
api_version_requests_total{version}counter (metrics module) in the version interceptor/middleware, expose per-version usage in admin, and track deprecation-warning counts; document the gate criteria for sunset.Acceptance criteria