Skip to content

docs: add configuration drift runbook (SECURESIGN-5169) - #195

Draft
miyunari wants to merge 1 commit into
mainfrom
securesign-5169-monitoring-runbook
Draft

miyunari wants to merge 1 commit into
mainfrom
securesign-5169-monitoring-runbook

Conversation

@miyunari

@miyunari miyunari commented Oct 15, 2026 •

Copy link
Copy Markdown
Member

Starts SECURESIGN-5169. No docs/ directory or operational docs exist yet.

Adds one problem-oriented runbook, docs/operations/runbooks/configuration-drift.md, structured around the incident: what drift is, why it happens, how to detect and confirm it, and how to resolve it. Metric names, labels, and behavior are taken from internal/metrics/metrics.go and internal/tracker/status_tracker.go.

Notes

  • Draft, single runbook — establishes the folder and format; more can follow.
  • Ticket named one monitoring-runbook.md; this uses a per-problem folder instead. SECURESIGN-5171 runbook_url annotations should point here.

@miyunari
miyunari force-pushed the securesign-5169-monitoring-runbook branch from 0bdcff6 to f275a66 Compare October 15, 2026 09:07
@miyunari miyunari changed the title docs: add monitoring runbooks for Prometheus metrics (SECURESIGN-5169) docs: add configuration drift runbook (SECURESIGN-5169) Oct 15, 2026
Add docs/operations/runbooks/configuration-drift.md, a problem-oriented
operational runbook for configuration drift: what it is, why it happens,
how to detect it, how to confirm it, and how to resolve it.

Grounded in internal/metrics/metrics.go and internal/tracker/status_tracker.go.

Signed-off-by: Nina Bongartz <pninak@web.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant