Skip to content

incident-report.md

Latest commit

 

History

History
57 lines (39 loc) · 1.28 KB

incident-report.md

File metadata and controls

57 lines (39 loc) · 1.28 KB
Raw

Incident Report: [INCIDENT-ID] — [Brief Title]

Incident ID: INCIDENT-___ Date Opened: YYYY-MM-DD HH:MM UTC Severity: [Critical / High / Medium / Low] Status: [Investigating / Mitigating / Monitoring / Resolved] Incident Commander: [Name] War Room Channel: #yieldvault-war-room Last Updated: YYYY-MM-DD HH:MM UTC

Affected Components

  • Backend API
  • Frontend
  • Database
  • RPC / Soroban nodes
  • Smart contracts
  • Other: ___

Runbook Used

  • [Runbook link or "N/A"]

Current Status

[One-paragraph summary of current state and ETA]

Live Timeline (append during incident)

Time (UTC) Actor Event
HH:MM Incident detected
HH:MM

Diagnostics Collected

  • Incident ticket created
  • Backend diagnostics bundle retrieved (/api/diagnostics/bundle)
  • RPC / node logs captured
  • Grafana dashboards linked

Communication Log

Time (UTC) Channel Message summary
HH:MM #yieldvault-incidents

Next Steps

  1. [Immediate action]
  2. [Follow-up]

When the incident is resolved, complete the Post-Mortem Template within 48 hours per the Postmortem Playbook.