Ask your incident assistant for the next useful check
In a hypothetical incident, errors began at 14:02 and the rollout started at 14:05. A reusable prompt helps an assistant turn that mismatch into a useful next check.
How-To
Practical methods you can take back to your team.
Follow the file your Linux service cannot write
A directory under /tmp can hold application recovery data. Follow the failing path through mounts, capacity and permissions to understand what the service actually sees.
Why more Linux workers can leave a small query waiting
A shared connection pool shows how a tuning change can finish more work while slowing some requests. Follow the wait, test the limit and compare both outcomes.
Customer reliability begins with the upload that did not finish
Keep the customer’s operation intact as a report becomes a ticket, an investigation and an answer about whether to wait or retry.
What happens after the disk alert wakes someone?
The warning is accurate, but the person allowed to add space is unavailable. Follow the response before deciding whether to page, queue the work or repair the gap.
Where to start with Google’s free SRE books
Choose a free Google SRE book and chapter for a current alerting, on-call or postmortem problem, then try one practice with your own team.
Make the canary test the change before sending more traffic
A quiet canary can still miss the operation that changed. Compare meaningful traffic, check service health and test withdrawal before expanding.
How to calculate mean time to detect from incident records
Calculate MTTD from three incident records. Keep customer reports, uncertain starts and the number of timed incidents visible.
Why the latency chart can improve while more customers time out
A faster latency line can lose the requests that timed out. Follow the counts, gauges and distributions back to the work they measured.
What an empty log search can tell you
A worker restarts mid-job. To decide whether to retry, the responder needs to know what the worker recorded and what made it into search.
An on-call rotation needs more than an evenly filled calendar
Follow a page through backup, specialist help, access and recovery to see what the whole on-call team can actually cover.
How a container image becomes a working service
Follow a packaged program through Kubernetes placement, health checks and resources, then trace the customer job it still needs to finish.