Prompting an assistant to investigate an incident
A reusable prompt connects observations, competing explanations and the next read-only check, so an incomplete record can still support useful investigation.
Articles
Guides, news and explanations about AI and reliable systems.
Not sure where to begin? Choose a short reading path, or browse at your own pace.
What an exhausted error budget changes
An error-budget policy connects measured reliability to release and planning choices, including a repair bundled with an unrelated feature.
Error-budget template: calculations and release-policy fields
Worked request and time-based budgets accompany an SLO record, release-policy template and exception log, keeping each calculation in its original units.
Finding a Linux write failure through paths and mounts
Directory conventions orient the investigation. Mounts, namespaces, inodes and service permissions explain which storage the failing process actually encounters.
Linux performance tuning starts with a bottleneck
A concurrency change can improve throughput and worsen tail latency. Comparable workloads and process-level limits help explain whether the change is worth keeping.
Coordinating incidents and bot actions in Slack
Incident channels connect responders to decisions and results. Write-capable bots also need precise action identifiers, duplicate handling and a route around a chat outage.
Comparing AIOps tools on responder work
Detection, correlation and remediation need different trials. The comparison includes specialist escalations, correction effort and the integrations left to maintain.
Finding the response delay AIOps can reduce
Evidence gathering, authorization and restoration can each hold up an incident. The timeline shows which kind of assistance could shorten the wait.
Customer reports reveal failures a fleet average can miss
An upload report becomes investigable through its operation, region and time window. That same detail connects the engineering result back to the customer.
Using ChatGPT for SRE analysis and writing
Runbook comparisons, timelines and draft updates provide checkable inputs for assistance. Incident closure also needs evidence about service recovery and unfinished work.
What makes an alert worth paging for
A capacity warning needs enough lead time and a reachable responder who can act. The alert review separates useful urgency from a missing response arrangement.
Where AI-generated tests fit in a release pipeline
A generated test can share the code’s mistaken assumption. Artifact identity and checks of the affected behavior explain what the passing result establishes.