otel-trace-analysis

To diagnose latency bottlenecks in distributed systems, this Skill parses OpenTelemetry trace JSON data to identify span relationships, timing anomalies, and dependency performance issues. It highlights critical paths and pinpoints the specific operations causing delays.

Yes, you can analyze OpenTelemetry traces for error propagation and retries. The Skill examines trace spans to track how errors propagate across services and identifies retry patterns to help locate the root cause of unexpected behavior.

The best way to quickly triage slow API response times is using the Skill's triage mode, which provides a rapid summary of the OpenTelemetry trace. This allows for fast issue identification when time is critical before conducting a full investigation.

Yes, you need to provide trace data in OpenTelemetry JSON format. The Skill requires parsing JSON trace data to evaluate span relationships, identify timing anomalies, and accurately diagnose distributed system performance issues.

Deep trace analysis provides a comprehensive breakdown of trace execution including critical paths and dependency performance, while a quick summary offers rapid issue identification. Both methods debug performance issues but differ in investigation depth.