3 min read
Interactive tools
Fourteen tools to learn by doing: how much downtime to tolerate, why the metrics bill blows up, which traces to keep, whether on-call is sustainable.
A pilot does not learn to handle an engine failure by reading the manual: they live through it in the simulator, safely. Some observability mechanisms are best understood the same way, by playing with them. What happens to the bill if you add one criterion to a metric? How many night-time pages can a team absorb? Does a tooling project really pay for itself? Each tool in this section answers a question of that kind, the one you will be asked in a steering committee or an incident review.
The tools run entirely in your browser and send no data anywhere. Those that remember your answers (RACI, NIS2, solution scorecard) keep them in this browser only. Every assumption is shown and editable. I encourage you to replace them with your own figures: a simulator is only as good as the assumptions you feed it.