Incident Desk Style
April 17, 2026 · View on GitHub
Style: Sharp operational palette, alert red and system slate, high-signal postmortem framing Best for: Incident reviews, outage notes, postmortems, service degradation updates, reliability summaries
Style Characteristics
| Property | Value |
|---|---|
| Background | Slate white #f6f8fa |
| Text | Ops charcoal #20252d |
| Accent | Incident red #d14343 |
| Secondary | Steel blue #5a6a7d |
| Muted | Log gray #818a95 |
| Tint | rgba(209,67,67,0.06) |
| Title Font | Inter, IBM Plex Sans, sans-serif |
| Body Font | Inter, Noto Sans SC, sans-serif |
| Surface | Operational and terse |
Template
The Failure Lasted 19 Minutes, but the Weak Signal Existed for Weeks
The visible outage came from a queue saturation event, but the deeper issue was threshold drift. Warning signals had already appeared in lag variance and retry concentration long before customer traffic amplified them into a page-worthy incident.
Short incidents often reveal long-running structural neglect
Primary Failure Mode
Consumer throughput fell below retry growth, which created a compounding queue wave once the malformed job pattern reappeared under higher load.
19m
User-visible degradation