docs: document deployment.logsHistory durable log history#39
Merged
Conversation
Add deployment.logsHistory — the durable 30-day sibling of the live, ephemeral deployment.logs — to the monitoring "Reading logs and status programmatically" section: since/until window, pod filter, oldest-first (forward) default or newest-first via reverse, opaque cursor pagination, best-effort lag behind live output by the capture flush interval, reuse of the deployment.logs permission, and log-bucket-only availability. Add CLI examples mirroring the existing deployment logs one (logs-history --since 24h and a --reverse variant) and make the live-vs-durable split explicit in the warning callout and Permissions subsection. Also surface deployment.logsHistory alongside deployment.logs in the MCP diagnose-a-failing-deploy recipe. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011d4bVuGLnCbcJD9ZvastPH
|
Preview deleted (PR closed). |
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
1 participant
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.
Documents the new (already-merged)
deployment.logsHistoryAPI action — the durable retrieval sibling of the live, ephemeraldeployment.logs.Changes
content/deployments/monitoring.md— in Reading logs and status programmatically:deployment.logsHistoryentry: durable 30-day history over asince/untilwindow,podfilter, oldest-first (forward) by default or newest-first withreverse, opaquecursorpagination (nextCursoruntil the window is exhausted), byte-budget cap (cappedByBytes), best-effort lag behind live output by the capture flush interval, reuse of thedeployment.logspermission, and log-bucket-only availability.deploys deployment logs ...one:deploys deployment logs-history --project acme --location gke.cluster-rcf2 --name web --since 24h--reverse.deployment.logsHistoryreuses the secret-bearingdeployment.logspermission.content/automation/mcp.md— surfacesdeployment.logsHistoryalongsidedeployment.logsin the diagnose-a-failing-deploy recipe.Verification
hugo --renderToMemorybuilds clean (55 pages, no warnings/errors).🤖 Generated with Claude Code