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.
Search articles
Search titles and article text.
How-To
Connect the signals with OpenTelemetry
Use instrumentation and context propagation to connect the evidence in an investigation.
News
OpenTelemetry’s Kubernetes milestone matters for AI agent tracing
The stable Kubernetes attributes processor helps connect AI-agent traces to their workloads. Check the metadata joins before upgrading.
AIOps
Use AIOps to shorten the part of incident response that is slow
Locate the delay, choose a bounded intervention, and measure recovery quality alongside elapsed time.
AIOps
The operational cost of AI tokens
Account for context limits, retries, latency, and the work behind a useful result.
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.
SRE
Error-budget template: calculations and release-policy fields
Adapt a complete SLO record, worked budget examples, and an exception log without confusing bad requests with minutes of downtime.
How-To
Use the 5 Whys without forcing an incident into one cause
Follow evidence through technical failure and incident response, then test whether the proposed correction changes the mechanism.
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
Observability logs: preserve the events an investigation needs
Design logs around useful events, searchable context, and a collection path whose failures are visible.
AIOps
Release gates that hold up under incident pressure
Turn reliability policy into a release decision with fresh evidence, limited exceptions, and a clear path to resuming normal changes.
How-To
Linux performance tuning starts with a bottleneck
Measure a representative workload, identify the limiting resource, and test one reversible change instead of applying a universal sysctl recipe.