trace-analytics
Trace Analytics lets you explore distributed traces and spans stored in OpenSearch to diagnose latency, errors, and service dependencies. Query span data with PPL, reconstruct trace trees, examine agent invocations and tool executions, and measure token usage across your system.
Trace Analytics helps you investigate distributed traces and spans in OpenSearch to debug performance and errors.
AI-generated summary based on this skill's SKILL.md
Install
opensearch-project/opensearch-agent-skills/trace-analytics · repository language: Python
git clone https://github.com/opensearch-project/opensearch-agent-skills
cp -r opensearch-agent-skills/skills/opensearch-skills/observability/trace-analytics ~/.claude/skills/trace-analyticsnpx skillfed install opensearch-project/opensearch-agent-skills/trace-analyticsFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I investigate distributed traces in OpenSearch?
Trace Analytics helps you investigate distributed traces in OpenSearch by letting you explore spans and trace data through an intuitive interface. You can query span information using PPL, reconstruct full trace trees by traceId, and correlate spans across services to understand request flow through your distributed system.
How can I find and debug slow spans in my traces?
Trace Analytics enables you to debug slow spans by analyzing trace latency and performance metrics. Filter spans by duration, identify performance bottlenecks, and examine individual span details to pinpoint which services or operations are causing delays in your distributed system.
What does Trace Analytics do for error analysis?
Trace Analytics helps you find and analyze error spans and exceptions in distributed systems. Search for spans with specific error status codes, examine exception details, and trace errors across service boundaries to understand how failures propagate through your OpenTelemetry-instrumented applications.
Can Trace Analytics track agent invocations and token usage?
Yes, Trace Analytics lets you track agent invocations and measure token usage from traces. Monitor tool executions, analyze gen_ai operation traces, and correlate token consumption across your system to understand resource usage patterns in agentic workflows.
How does Trace Analytics help with service dependency mapping?
Trace Analytics lets you query service maps and understand service dependencies by visualizing how services communicate through distributed traces. Examine service topology, identify inter-service relationships, and troubleshoot slow distributed traces by understanding the full dependency graph.
What's required to set up Trace Analytics in OpenSearch?
Trace Analytics works with OpenSearch trace data from OpenTelemetry instrumentation. Store your OTEL spans in OpenSearch, then use Trace Analytics to query and visualize the trace tree. The skill operates under Apache-2.0 license and integrates with your existing OpenSearch deployment.
SKILL.md
rendered from the published skill — quoted content, verbatim
OpenSearch Trace Analytics
You are an OpenSearch trace analytics specialist. You help users investigate distributed traces, analyze span performance, debug errors, and understand service dependencies.
Prerequisites
- A running OpenSearch cluster with OTel trace data (typically
otel-v1-apm-span-*) uvinstalled (for running helper scripts)
Optional MCP Servers
```json { "mcpServers": { "ddg-search": { "command": "uvx", "args":
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 2 files
skills/opensearch-skills/observability/trace-analytics/SKILL.md
skills/opensearch-skills/observability/trace-analytics/traces.md