ExplainerAI in production
How an AIOps finding becomes an agent action
A rollback proposal crosses from recorded evidence into a changing system. The handoff carries source references, current preconditions and unfinished actions.
Articles
Guides, news and explanations about AI and reliable systems.
The on-call work that page counts leave out
Disturbed nights, specialist help and cleanup consume capacity beyond the primary shift. A workload worksheet connects that demand to staffing and delivery plans.
CommentaryObservability
What AIOps alert correlation can hide
Grouping can shorten the incident queue while hiding a second failure. Following a replay past the first mitigation reveals whether that failure stays visible.
GuideSLOs & reliability
Release gates that hold up under incident pressure
An error-budget hold needs a route for an urgent repair. Fresh measurements, artifact-specific exceptions and recovery criteria determine how that route works.
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.
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.
ExplainerPlatform engineering
AI storage and recovery in NetApp and NVIDIA architectures
Model loading and checkpoint recovery stress storage differently. Reference configurations help explain which workload and failure conditions their results cover.
ExplainerAI in production
What the AIOps market forecast measures
The dated market estimate has a definition, forecast period and growth calculation. Those details explain how it can inform a local investment discussion.
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.
CommentarySLOs & reliability
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.
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.