·2 min read
HTTP, TCP, DNS, SSL, what each check really tells you
The four basic monitoring checks each answer a different question about your service. What HTTP, TCP, DNS, and SSL checks actually tell you, and when to use each.
Incident articles, page 8
More articles on incident management, monitoring, and on-call.
·5 min read
How Deployment Tracking Cuts Incident Response Time
Most outages follow a recent change. Surface deployments inside the incident view so responders stop hunting Slack and GitHub mid-page.
·6 min read
Shadow On-Call: How to Onboard New Engineers Without Burning Them Out
Shadow on-call lets new engineers learn the rotation before they own it. Structure, readiness criteria, and why skipping the shadow creates long-term aversion.
·6 min read
What Happens to Your Status Page When Your Product Goes Down?
If your status page shares fate with your product, customers hit a browser error when they need an update most. Host it independently and test that path.
·7 min read
How to Build an On-Call Schedule for the First Time
Formalize on-call when informal Slack paging starts missing alerts. Start with a weekly rotation, a secondary, and a short readiness checklist.
·6 min read
SLA vs SLO vs SLI: What Each One Means and Why the Difference Matters
SLI is what you measure, SLO is the internal target, SLA is the customer contract. Mixing them up creates false confidence and real credit risk.