Guides
7 guides on reliability. Practical writing from the team building Atlas, useful whether or not you buy anything.
Every method for finding causes has a failure mode of its own. Know what each is good for, use more than one, and be wary of any that offers a single tidy answer.
An indicator measures how the service behaves, an objective says how good it should be, and an agreement says what you promise. Keeping them apart makes reliability a decision rather than a feeling.
When most pages need no action, people learn to ignore pages, including the one that matters. Alert fatigue is a reliability risk and a retention risk at once.
There is no single best on-call schedule. There are patterns that suit particular team sizes, locations and paging volumes. Here are five, with the trade-offs of each.
On-call management decides who answers when something breaks, what happens if they do not, and how to ask people to carry that duty without wearing them out.
MTTR, MTTA and MTTD are the most quoted incident metrics and the most often confused. Fix the definitions first, then use the numbers as a signal about the system.
Incident management is how a team detects a problem, responds in an organised way, tells the people affected and learns enough to prevent a repeat. This guide covers the whole process.
Ready when you are
Atlas brings tasks, projects, CRM, contracts, e-signature, PDF tools, and analytics into one workspace. Start free.