GuideIncident response
Keeping incident state consistent across PagerDuty, Jira and Slack
A reference design for duplicate deliveries and partial API success, with durable incident identifiers and summaries drawn from the resulting record.
Guides
Walkthroughs for observability, incident response and AI-assisted operations.
Browse guides with article filtersAIOps fundamentals
Start with what AI can do for operations, and where judgment still matters.
Read AIOps fundamentalsObservability for SRE
Make metrics, logs and traces work together.
Read Observability for SREIncident management with AI
Build an incident response practice that learns.
Read Incident management with AIPractical articles
Instructions, examples and implementation notes.
GuideObservability
Grafana dashboards for incident response
Regional failures can disappear in fleet averages. Grafana queries, population labels and linked traces help responders find the affected requests.
GuideAI in production
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.
GuideSLOs & reliability
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.
GuidePlatform engineering
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.
GuidePlatform engineering
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.
GuideIncident response
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.
GuideAI in production
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.
GuideIncident response
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.
GuideIncident response
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.
GuideObservability
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.
GuidePlatform engineering
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.