observability

Correlating logs, metrics, and traces requires a structured analysis workflow that aligns signals across backends to identify root causes. This skill guides teams through incident response by applying recommended queries and sampling strategies to pinpoint bottlenecks.

Yes, this observability analysis approach works with Datadog, Splunk, Elasticsearch, and OpenSearch. It also supports Coralogix, Honeycomb, and Jaeger, allowing teams to perform cross-backend signal correlation during on-call investigations.

The best way to investigate high latency incidents is to align traces with metrics to locate bottlenecks and dependency issues. This skill provides a step-by-step investigation playbook using aggregated statistics and targeted sampling to triage production anomalies.

Detecting anomalies and failure clusters in production systems involves analyzing observability data for unusual patterns and spikes. This skill provides anomaly detection guidance by correlating logs, metrics, and traces to identify failure clusters and prioritize fixes.

Yes, you can use this methodology for post-mortem analysis after an on-call incident. It applies a structured observability workflow to correlate signals from multiple backends, helping teams review aggregated statistics and document root causes effectively.

Triage incidents using aggregated statistics and targeted sampling by following a structured investigation playbook. This skill enforces a step-by-step methodology to query observability data across logs, metrics, and traces, ensuring effective root cause identification.