docs: application error detection (Sentry-lite)#40
Merged
Conversation
Add a Deployments-section page documenting the new application error detection feature: deploys.app mines deployment logs for stack traces, groups identical traces into deduplicated issues with counts, first/last seen, a representative stack, and an open/resolved/reopened/muted triage lifecycle. Covers the Console Errors tab, the deployment.error notification event, the deployment.errors/errorGet/errorUpdate API (gated by deployment.logs), the six kinds, and ~30-day retention. Registers the new actions in the API catalog, adds the deployment errors CLI verb and a light MCP mention, and cross-links from the monitoring page. PR 7/7 of error detection (SPEC-error-detection.md). 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.
PR 7/7 of error detection (
SPEC-error-detection.md) — the documentation page for the feature.What this documents
deploys.app automatically mines a deployment's durable logs for application-level stack traces (Go panics; Java/Python/Node/Ruby exceptions; a generic fallback) and groups identical traces into deduplicated issues with an occurrence count, first/last-seen, a representative stack, and recent occurrences — with an open → resolved → reopened/regressed (plus muted) triage lifecycle. Detection runs server-side from the captured logs, so it lags live output by roughly a minute, and only stack traces become issues (lone
ERRORlines stay in the logs).Pages added / changed
content/deployments/error-detection.md(new, weight 9 — right after Monitoring) — the feature page:deployment.health(infra) anddeployment.status(pod).deployment.errorchange event delivered to webhook/Discord channels; subscribe todeployment.errorordeployment.*. Message carries only the exception type + reason, never the stack (secret-safe).deployment.errors,deployment.errorGet,deployment.errorUpdate(params + response), all gated bydeployment.logs; the sixkinds.deploys deployment errors) and MCP mention.content/api/conventions.md— registers the three new actions in the Deployments function catalog.content/automation/cli.md— addserrorsto thedeploymentnamespace actions.content/automation/mcp.md— short pointer todeployment.errors/errorGetin the diagnose-a-failing-deploy recipe.content/deployments/monitoring.md— cross-link from the Logs section to the new page.Verification
hugo --minifybuilds clean (56 pages, no errors/warnings)./scrutinizerun: every API field name, parameter, status value, permission, event name, lag figure, and retention window checked against the contract and the SPEC.🤖 Generated with Claude Code
https://claude.ai/code/session_011d4bVuGLnCbcJD9ZvastPH