Monitoring, alerting, and on-call runbook

[truthixify]

Tier: L (5-7 days) | Type: docs

Context. guides/ops/self-hosted-deployment.mdx (Wave 7) walks getting contracts up. Nothing today tells the operator what to watch, when to page, or how to respond. Teams running Wraith in production need a full runbook: healthy metric baselines, ready-to-import dashboards, alert rules, incident playbooks, and a tabletop exercise. This is more than a page; it is a bundle of ops artifacts, hence the larger tier.

Scope.

• New guides/ops/monitoring-and-on-call.mdx.
• Key metrics: RPC latency, announcement-lag, indexer backlog, watcher event-drop rate, contract error rate.
• Grafana dashboard JSON in guides/ops/dashboards/ (one for RPC, one for indexer, one for contracts).
• Prometheus alerting rules file with rationale per rule.
• Six named incident playbooks: RPC outage, Horizon backpressure, indexer stall, contract mispublish, watcher drop-spike, key-rotation incident.
• Sev matrix mapping incident types to response SLA, cross-linked with the auditor guide's severity ladder.
• Tabletop exercise script for a quarterly drill.

Acceptance.

• Reviewer imports each dashboard into a Grafana instance without error
• Alert rules validated with promtool check rules
• Reviewer walks one playbook end-to-end on a staging deployment
• Renders in mint dev
• Passes Compile docs snippets CI
• Cross-linked with self-hosted-deployment.mdx and reference/auditor-guide.mdx
• Nav entry under Operations

Files. guides/ops/monitoring-and-on-call.mdx (new), guides/ops/dashboards/ (new), guides/ops/alerts/ (new), docs.json.

[ogundeleoluwaferanmi35]

@ogundeleoluwaferanmi35 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

please assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ogundeleoluwaferanmi35 to this issue.

[code3ks]

@code3ks has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello maintainer i would like to work on this.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @code3ks to this issue.

[drips-wave]

Congratulations, @code3ks! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @code3ks: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @code3ks as part of the Stellar Wave Program's 8th Wave 🥳

😎 @code3ks: You earned 100 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.