feat(server-ng): enforce PAT limits and expose Prometheus metrics - #3773
Open
hubcio wants to merge 1 commit into
Open
feat(server-ng): enforce PAT limits and expose Prometheus metrics#3773hubcio wants to merge 1 commit into
hubcio wants to merge 1 commit into
Conversation
Enforce max_tokens_per_user at PAT create ingress on both planes and add a real /metrics endpoint with legacy gauge parity. Binary-plane PAT rewrite errors used to be dropped silently (the client hung until timeout); they now return a typed deny. The segments gauge reports the correct scrape-time count instead of reproducing the legacy drift bug.
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Enforce max_tokens_per_user at PAT create ingress on both planes and
add a real /metrics endpoint with legacy gauge parity. Binary-plane
PAT rewrite errors used to be dropped silently (the client hung until
timeout); they now return a typed deny. The segments gauge reports the
correct scrape-time count instead of reproducing the legacy drift
bug.