P2: Operations runbook — SLOs, capacity, incidents, failover (#180)#197
Open
dkijania wants to merge 1 commit into
Open
P2: Operations runbook — SLOs, capacity, incidents, failover (#180)#197dkijania wants to merge 1 commit into
dkijania wants to merge 1 commit into
Conversation
There was one benchmark data point but no runbook, SLOs, or documented failure-mode response. Add docs/runbook.md: - Starting SLOs (availability, p50/p99 latency, error rate). - What to watch (the /metrics RED signals, readiness, structured logs) and suggested alerts. - Scaling & capacity guidance — stateless horizontal scaling, Postgres as the real ceiling, pool-vs-max_connections math. - Multi-host Postgres failover semantics and recovery expectations. - A common-incidents table mapping symptoms to causes and actions. - Deploy/rollback notes tied to graceful shutdown and readiness gating. Linked from the README. An automated replica-failover test is noted as a follow-up (needs a multi-host DB harness). Closes #180. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QSuak9smCHbp4N17xjjLF6
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.
What & why
Part of the production-readiness epic (#163). Closes #180.
There was one benchmark data point but no runbook, SLOs, or documented failure-mode response.
Adds
docs/runbook.md/metricsRED signals, readiness, structured logs, and suggested alert thresholds.replicas × PG_MAX_CONNECTIONSvs DBmax_connectionsmath.Linked from the README. References observability/config features delivered by the sibling PRs. An automated replica-failover test is noted as a follow-up (needs a multi-host DB harness), so the doc is the deliverable here.
Testing
Docs only.
prettier --debug-check .clean. No application code changed.🤖 Generated with Claude Code