analyze-traces

Analyze OpenTelemetry traces and structured logs to debug service errors and latency issues.

7|3|Updated Nov 26, 2025

Search Tags:#performance #debugging #logs #distributed-systems #opentelemetry #traces

Ready to run

npx skills add https://github.com/jagreehal/autotel --skill analyze-traces

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: analyze-traces
Source: https://github.com/jagreehal/autotel/tree/main/packages/autotel/skills/analyze-traces
Command: npx skills add https://github.com/jagreehal/autotel --skill analyze-traces

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables users to analyze and interpret OpenTelemetry traces and structured logs from autotel services, aiding in debugging errors and investigating latency issues.

Core Features & Use Cases

Trace Debugging: Helps identify root causes of failed requests and performance bottlenecks by analyzing trace data from various backends and in-memory exports.
Latency Investigation: Enables detailed waterfall analysis to spot slow operations and resource contention.
Request Tracking: Facilitates following a user request across multiple services using correlation IDs and trace information, supporting complex distributed systems.

Quick Start

Analyze an OpenTelemetry trace dump to identify the root cause of an error.

Frequently Asked Questions about analyze-traces

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I analyze OpenTelemetry traces to debug service errors?▼

To analyze OpenTelemetry traces for debugging service errors, you process trace dumps and structured logs to identify root causes of failed requests. This includes reviewing in-memory exports and local JSON dumps to pinpoint exact failure points across distributed systems.

What is the best way to investigate latency issues using distributed traces?▼

Investigating latency issues with distributed traces involves performing a detailed waterfall analysis to spot slow operations and resource contention. By examining the trace data, you can isolate specific spans causing performance bottlenecks within the request flow.

Can I track a user request across multiple services using OpenTelemetry?▼

Yes, you can track a user request across multiple services by following correlation IDs and trace information within the OpenTelemetry data. This supports complex distributed systems by mapping the entire request flow across different components.

Does this approach work with local JSON dumps and in-memory OTLP exports?▼

Yes, this approach works with local JSON dumps and in-memory OTLP exports to facilitate troubleshooting and hygiene audits. It supports various backend formats, ensuring comprehensive insight into trace data and artifact relationships without requiring a live backend.