skills.rest
opensearch-project
opensearch-projectOFFICIAL
Explore all skills by this author →
WebsiteGitHub

trace-analytics

Analyze OpenSearch distributed traces and spans to identify bottlenecks and failures.

40|41|Updated Apr 1, 2026
Search Tags:#trace#opentelemetry#distributed-tracing#otel#opensearch#ppl#service-map
One-click install
npx skills add https://github.com/opensearch-project/opensearch-agent-skills --skill trace-analytics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trace-analytics
Source: https://github.com/opensearch-project/opensearch-agent-skills/tree/main/skills/opensearch-skills/observability/trace-analytics
Command: npx skills add https://github.com/opensearch-project/opensearch-agent-skills --skill trace-analytics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzing distributed traces and spans stored in OpenSearch can be complex; this skill provides guidance to efficiently inspect, filter, and correlate trace data to diagnose performance issues and architectural bottlenecks.

Core Features & Use Cases

  • Discover and connect to OpenSearch trace indices (otel-v1-apm-span-, otel-v2-apm-service-map-) and inspect their schema to ground queries.
  • Execute PPL-based queries to identify slow spans, error spans, token usage, and to reconstruct complete trace trees.
  • Generate insights into service topology and agent interactions via trace data and service maps for debugging distributed systems.

Quick Start

Query a specific traceId to identify slow spans and map service interactions in your OpenSearch cluster.

Frequently Asked Questions about trace-analytics

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

FAQPage Schema
How do I analyze OpenTelemetry traces stored in OpenSearch to find slow spans?▼

To analyze OpenTelemetry traces in OpenSearch, query distributed spans using PPL to identify slow or failed operations. This reveals latency bottlenecks across your service architecture for targeted debugging.

What's the best way to map service dependencies using distributed tracing data?▼

Mapping service dependencies uses distributed tracing data to reconstruct topology and agent interactions. Analyzing service maps in OpenSearch visualizes architectural bottlenecks and highlights structural relationships within your system.

Do I need a running OpenSearch cluster to query OpenTelemetry trace data?▼

Yes, you need a running OpenSearch cluster. This environment stores the OpenTelemetry trace data and provides the PPL or SQL capabilities required to query spans and service maps.

Can I use PPL to reconstruct a complete trace tree from span indices?▼

Yes, PPL reconstructs complete trace trees from span indices. Querying specific trace IDs across OpenSearch trace indices correlates individual spans to map service interactions and pinpoint failures.

How does analyzing distributed traces help diagnose architectural bottlenecks?▼

Analyzing distributed traces diagnoses bottlenecks by inspecting spans across multiple services. Correlating this trace data exposes error spans and slow dependencies, clarifying performance issues within distributed systems.

Related Skills

Explore More Data & Analytics Skills→
opensearch-projectopensearch-project
34

traces

Query OpenSearch trace data with PPL to analyze agent invocations and errors.

Official
Intermediate
DouwMarxDouwMarx

productionization

Convert validated evaluations into automated monitoring systems with dashboards and alerting.

Community
Advanced
opensearch-projectopensearch-project
34

ppl-reference

Author PPL queries for OpenSearch observability data with commands and functions.

Official
Advanced
opensearch-projectopensearch-project
40

observability

Analyze and correlate log and trace data in OpenSearch clusters.

Official
Intermediate