MCP For Claude Marketplace
OpenTelemetry Trace Latency Analyzer

OpenTelemetry Trace Latency Analyzer MCP Connector for Claude

A+

Analyze OpenTelemetry traces to identify latency bottlenecks and critical path inefficiencies.

3 tools Official Updated Oct 1, 2026 Official Vinkius Partner
More Details Connect to Claude

This MCP server provides a diagnostic engine for deconstructing OpenTelemetry-style traces. By analyzing spans with start/end timestamps and parent-child relationships, it computes critical-path duration, per-span self-time (excluding children), span-count and depth per trace, longest-chain bottleneck identification, and percentage of total trace duration attributable to each service or span-name group. Use analyze_trace_latency for high-level metrics, identify_bottlenecks to find slow spans, and get_service_distribution to see latency distribution across services.

opentelemetrytracinglatencybottleneckmicroservices

3 tools expose this connector's capabilities to your AI agent.

analyze_trace_latency

Analyze trace spans for latency metrics

get_service_distribution

Calculate average latency per service/span name

identify_bottlenecks

Identify spans that exceed a latency threshold

See how to talk to your AI agent using OpenTelemetry Trace Latency Analyzer.

Analyze this trace for latency: [{"id": "1", "parentID": null, "serviceName": "gateway", "spanName": "entry", "start": 1000, "end": 2000}, {"id": "2", "parentID": "1", "serviceName": "auth", "spanName": "validate", "start": 1100, "end": 1500}]

The trace analysis shows a total duration of 1000ms. The gateway entry span has an average latency of 1000ms, while the auth validation span contributes 400ms.

Identify bottlenecks in this trace where spans exceed 50ms: [{"id": "1", "parentID": null, "serviceName": "api", "spanName": "root", "start": 0, "end": 200}, {"id": "2", "parentID": "1", "serviceName": "db", "spanName": "query", "start": 10, "end": 150}]

The following bottleneck was identified: the `db` service span `query` contributed 140ms of self-time, exceeding your 50ms threshold.

What is the latency distribution for these spans?

The service distribution shows that 'auth-service' has an average latency of 45ms and 'payment-service' has an average latency of 120ms.

It supports OpenTelemetry-style traces where each span includes a unique identifier, parent ID, service name, span name, and start/end timestamps.

Related Connectors

Infrastructure Capex Analyzer

Infrastructure Capex Analyzer MCP

4 tools Official

Analyze maintenance vs growth capex and infrastructure lifecycle health.

A+ View details →
NEW
Revenue Per Customer Analytics

Revenue Per Customer Analytics MCP

4 tools Official

Analyze average revenue per customer across timeframes and segments.

A+ View details →
Accelerator Time-to-Market

Accelerator Time-to-Market MCP

3 tools Official

Quantify the impact of acceleration on time-to-market and market opportunity.

A+ View details →
Agent Cost Allocation Engine

Agent Cost Allocation Engine MCP

3 tools Official

Deterministic cost allocation and chargeback calculator for multi-agent systems.

A+ View details →