Context
The Grafana HTTP dashboard identifies traffic by HTTP method and FastAPI route template. This is useful for debugging, but administrators cannot always understand the operation represented by routes with placeholders or fallback labels.
Problem
The metrics do not expose a stable human-readable operation name. Grafana must therefore show raw route templates or maintain a brittle route-to-label mapping that will drift as the API evolves.
Expected behavior
HTTP metrics expose a bounded, stable operation name for registered routes and a clear fallback for unmatched requests. Dashboards can display that operation alongside the method and route without creating labels from concrete partition names, file IDs, or other request values.
Context
The Grafana HTTP dashboard identifies traffic by HTTP method and FastAPI route template. This is useful for debugging, but administrators cannot always understand the operation represented by routes with placeholders or fallback labels.
Problem
The metrics do not expose a stable human-readable operation name. Grafana must therefore show raw route templates or maintain a brittle route-to-label mapping that will drift as the API evolves.
Expected behavior
HTTP metrics expose a bounded, stable operation name for registered routes and a clear fallback for unmatched requests. Dashboards can display that operation alongside the method and route without creating labels from concrete partition names, file IDs, or other request values.