← Back to guidesGuide

Build Kubernetes incident timelines from OTel signals without inventing the root cause

A practical workflow to align metrics, logs, traces, and Kubernetes events when HPA, retries, and queues blur the incident story.

Learn how to reconstruct an operational timeline with OpenTelemetry, Prometheus, logs, and Kubernetes events so you can separate cause, symptom, and mitigation without relying on intuition.

Created: July 24, 2026

Published: July 24, 2026

Estimated time35 min

LevelIntermediate

Before you startRead access to Prometheus or Grafana Explore

PlatformsLinux

WhatsApp X LinkedIn

Linux

CLI workflow to capture Kubernetes events, PromQL queries, logs, and traces inside one shared time window.

kubectlcurljqPrometheus accesslogs/traces access

Export sorted events

kubectl get events -n prod-eu-a --sort-by=.lastTimestamp -o wide

Inspect HPA state

kubectl describe hpa checkout-api -n prod-eu-a

Query Prometheus errors

curl -G 'http://prometheus:9090/api/v1/query_range' --data-urlencode 'query=sum by (service)(rate(http_server_requests_total{status=~"5.."}[5m]))' --data-urlencode 'start=2026-07-24T07:40:00Z' --data-urlencode 'end=2026-07-24T08:10:00Z' --data-urlencode 'step=30s'

Also available inConstruir timelines de incidentes en Kubernetes con señales OTel sin inventar la causa raíz

Content locked

This guide requires both steps before full content is available.

○Click “Like” on this guide.
○Share on WhatsApp, X, LinkedIn, or copy the link.

Access is automatically unlocked as soon as both steps are completed.