The Observability Moonshot

How the story begins

NarratorMonday, 9 AM. Wolfy loved logs, metrics, traces, and knowing why production was unhappy before Slack discovered it. He also measured his own life: heart rate, posture, espresso, and the throughput of an animatronic tail. Everything with a sensor seemed to deserve a dashboard.

WolfyLeadership wants one pane of glass for production health. Approved sources, useful signals, readable panels. Simple. I create the executive overview and connect the data. One personal Prometheus endpoint remains checked in my local configuration, waiting to make a surprisingly persuasive argument for reviewing defaults.

NarratorAt 10:13, the office television displayed 184-millisecond API latency, a 0.02 percent checkout error rate, queue depth thirty-seven, and 412 tail wags per minute. Four executives, two directors, and a tired finance colleague stared. The CFO asked whether 412 was good.

WolfyThe correct answer is context-dependent. The useful answer is that a personal data source has crossed a boundary. I can acknowledge that immediately, or first inspect the selector and verify exactly what the dashboard is showing before explaining it to the room.

What happens next is your call. Play now ▸

How you play

• Three decisions shape how Wolfy handles the incident, with composure, candor or curiosity.
• Two endings, with different consequence scenes along each route.
• Fourteen original anime-style paintings and an adaptive synthesized soundtrack.
• Plays in 8–12 min, free in your browser with no download or account. Progress saves on your device.