Add an internal ateapi statusz page - #1596
Draft
Adhita Selvaraj (swiftdiaries) wants to merge 4 commits into
Draft
Add an internal ateapi statusz page#1596Adhita Selvaraj (swiftdiaries) wants to merge 4 commits into
Adhita Selvaraj (swiftdiaries) wants to merge 4 commits into
Conversation
Expose build, readiness, listener settings, projected configuration, and bounded worker-pool counts through one status model and embedded dashboard. Keep cache failures distinct from an empty fleet and cover rendering and snapshot behavior with tests.
Add a configurable status port and project resolved flags through a closed display policy before handing them to the dashboard. Share existing readiness and worker-cache state, keep status available through the gRPC drain, and bound HTTP shutdown.
Add the named status port to the deployment and headless API Service. Document replica-local data, redaction, HTML/JSON access, and disabling the listener so operators can inspect an API replica through port-forwarding.
Adhita Selvaraj (swiftdiaries)
changed the title
Contributor
Author
Collaborator
|
+1 I love statusz pages :-) |
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
2 participants
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.
tried to take a first pass at this. If the general direction, shape looks good then I can follow up with a PR on top of this for metrics similar to
ate-routerScreenshot
AI-generated PR description
Adds an internal ateapi
/statuszfoundation for inspecting one process: HTML and JSON share build/version, uptime, live readiness, listener/drain settings, and safely redacted resolved configuration.The endpoint uses a dedicated
--status-portlistener (default 4040; nonpositive disables it), remains available through gRPC drain, and is exposed through the internal API Service. Environment-resolved values, credentials, and configuration paths follow a closed display policy.This PR contains no worker-count aggregation, PostgreSQL pool snapshots, or RPC-history recorder. All diagnostic aggregation and its five-second sampling cache are isolated on a separate local branch for review; no second PR has been opened. The earlier screenshot above predates this split and includes the worker section that has now moved to that branch.
Partially addresses #1458.
Validation at
6ba881102eee10626c83b4b14bd686b0ac533892: focused ateapi/statusz race tests passed, and allhack/verify-all.shchecks passed. Fullmake verifyreached an unrelatedinternal/childreapsubprocess timing failure (p90 232 ms against 160 ms); isolated reruns failed twice and passed once, so the aggregate command is not reported as passing. No live-cluster deployment or E2E validation was performed.