AIOps
Observability With AIOps: A Practical Evaluation Guide
Use AIOps to connect operational evidence, then test whether it improves investigation without hiding missing signals or unsupported conclusions.
Search articles
Search titles and article text.
AIOps
NotebookLM for SRE: build a source-backed incident dossier
Use a curated notebook to compare runbooks and incident evidence, while keeping citations, freshness, and operational authority in view.
News
Splunk agent observability: follow the work, then the bill
Splunk’s September release connects agent evaluation and cost monitoring. The useful test is whether a responder can trace spending back to an outcome.
AIOps
GPU capacity depends on power and cooling
When inference slows without obvious application errors, test physical constraints alongside queueing, workload changes, and software regressions.
AIOps
Evaluate Claude Opus 4.6 for operational work
Test evidence retrieval, long-session consistency, tool boundaries, and cost before letting a model influence production changes.
How-To
Mean time to detect: calculate MTTD and expose measurement gaps
Use consistent onset and discovery timestamps, include customer-reported incidents, and interpret the average with its sample and uncertainty.
How-To
Metrics for observability: choose the question before the chart
Counters, gauges, and distributions answer different questions. Build metrics that preserve scope, denominators, and the evidence behind an incident.
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.