AIOps
Route support tickets with NLP and a reliable fallback
Build a ticket-routing evaluation around real ownership, uncertain cases, and correction cost. Start with an honest baseline before adding a model.
Articles
Original AIOpsSRE articles, newest first. Find current releases and industry coverage in News.
AIOps
Continuous monitoring needs a visible stale-data state
Design continuous monitoring around freshness, coverage, delivery, and response ownership before adding analysis or automation.
SRE
Service level objectives: define the experience you intend to protect
Choose an SLI, target, and evaluation window that reflect user experience, then agree on the decisions an SLO result will change.
How-To
Read a distributed trace without mistaking it for the whole system
Understand spans, parent-child relationships, retries, and missing evidence so traces support a careful diagnosis.
SRE
SRE feedback loops: check whether the signal still means the same thing
Connect telemetry, customer reports, decisions, and verification so improvements in a dashboard reflect improvements in the service.
SRE
Error budgets: calculate the allowance and agree how to use it
An error budget translates an SLO into an allowed amount of bad service. Its value comes from the decisions attached to consumption and burn rate.
SRE
SRE KPIs: measure outcomes, response, and operational cost
Choose a small set of reliability indicators with clear definitions, useful distributions, and an explicit decision attached to each.
How-To
Read Google’s free SRE books with an operational question in mind
Use the free SRE books as references for a concrete service problem, then adapt and test the practices against your own constraints.