Repository navigation
fix: bound AI Gateway method and route metric labels - #29722
Closed
Conversation
Contributor
Docs previewCheck off each page once it's been reviewed. If a page changes in a later push, its checkbox clears automatically so it gets a fresh look. Pages not yet wired into the docs navigation aren't listed here. |
pawbana
force-pushed
the
pawel/aigov-615-reverse-proxy-handler-with-recorder-lifecycle-and-key-4
branch
7 times, most recently
from
September 24, 2026 17:11
793c924 to
90b24cd
Compare
Collaborator
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Use registered route patterns and bounded HTTP method values for interception and passthrough metrics. Preserve one passthrough transport per provider and document the label contract.
Part 5/10 of AIGOV-615, split from #29656. Stacked on #29721; review only the incremental diff. One commit in this slice. The original PR remains a reference draft.
Implementation plan and review scope
Apply the method helper without changing metric families or breaker behavior. Cover variable paths, unknown methods, and transport reuse with shared fixtures.
Sequence: mechanical moves; helper changes; security; replay; metrics; transport cancellation; shutdown; dormant forwarding; complete dormant recording; final activation. The numbered branches are stacked for publication, not evidence that every patch has a runtime dependency on its predecessor.
Each slice received a dedicated GPT 5.6 Sol concision review before publication. Preserve regression outcomes rather than removing tests only for line count.
Generated by Coder Agents on behalf of @pawbana.