Skip to content

No telemetry for deprecated-version usage to guide the v1 sunset #1244

Description

@nanaf6203-bit

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programapiAPI relatedenhancementNew feature or requestmonitoringMonitoring

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions