Skip to content
Vinkius

OpenTelemetry Trace Analyzer Connector for AI agents.

3 live capabilities

Find and fix performance bottlenecks in your distributed microservices.

Live agent request OpenTelemetry Trace Analyzer / Connector

Waiting for input…

AI Agent

Why people use OpenTelemetry Trace Analyzer

OpenTelemetry Trace Latency Analyzer for Bottleneck Detection

This Connector puts that logic into your AI client. You just drop the trace data in, and it handles the math. It tells you the critical path, the self-time, and the exact service distribution in one go.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • Visual Studio Code
  • Windsurf

What Vinkius changes

You get a surgical breakdown of where your request time is actually going.

Use it from Claude, ChatGPT, Cursor or another AI client you already have.

One account · 6,100+ Connectors

  1. Real-world use case 01

    A slow checkout flow

    An engineer sees a 5s checkout.

  2. Real-world use case 02

    Cost optimization

    A lead wants to see where to scale.

  3. Real-world use case 03

    Debug a ghost lag

    A dev thinks a service is slow, but it's just waiting on a slow downstream API.

Complete set · 3capabilities

The complete OpenTelemetry Trace Analyzer capability set.

These are the exact actions your AI can choose when you ask it to work with OpenTelemetry Trace Analyzer.

Capability set01 / 01

01—03

3 capabilities in this set.

Part of 3 available through OpenTelemetry Trace Analyzer.

  1. 01 Capability

    Analyze trace latency

    Breaks down the trace to show high-level metrics like total duration and span counts. It gives you a bird's-eye view of the request flow.

  2. 02 Capability

    Identify bottlenecks

    Flags specific spans that exceed a time threshold you set. This points you directly at the noisy neighbors or slow queries.

  3. 03 Capability

    Get service distribution

    Calculates the average latency for every service or span name in your trace. It helps you see which part of your stack is the heaviest.

Set up in minutes

One URL. Then ask OpenTelemetry Trace Analyzer to work.

Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use OpenTelemetry Trace Analyzer from the conversation.

Choose your client

Live preview
Advanced clients IDE · CLI

Claude · Web + desktop

Official guide ↗

Connector URL · ready to paste

Streamable HTTP
https://edge.vinkius.com/vk_preview_agOS3XqPfYKQCHw4us6xxbEWEsZ0GDWuybsYlRLe/mcp
  1. Step 01

    Open Connectors

    In Claude Web or Claude Desktop, open Settings and choose Connectors.

  2. Step 02

    Add the URL

    Choose Add custom connector, name it OpenTelemetry Trace Analyzer, and paste the URL above.

  3. Step 03

    Turn it on in chat

    Select +, open Connectors, and enable OpenTelemetry Trace Analyzer for the conversation.

Where the request belongs

Work OpenTelemetry Trace Analyzer can move forward.

Built around the request

This is for the engineers who live in the weeds of distributed systems. It's for the people who need to prove exactly where a bottleneck is located without spending hours manually calculating spans.

01

SRE

The person getting paged at 3 AM because a core API is lagging and needs to find the culprit fast.

02

Backend Developer

The engineer trying to optimize a complex microservice chain and needing to see where the time is actually spent.

03

Performance Engineer

The specialist tasked with shaving milliseconds off a global request by identifying the heaviest spans.

04

DevOps Engineer

The person managing high-traffic infrastructure who needs to justify scaling needs with hard latency data.

Bring your own AI

Change the model, client or framework. Keep OpenTelemetry Trace Analyzer connected.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • VS Code
  • Windsurf
  • ZCode
  • Cline
  • Zed
  • Continue
  • Kiro
  • Roo Code
  • Zencoder
  • Goose
  • Void
  • Augment Code
  • Amp
  • Qodo
  • Tabnine
  • Pieces
  • Sourcegraph Cody
  • JetBrains
  • Warp
  • Amazon Q
  • Antigravity
  • BoltAI
  • Raycast
  • Jan
  • LM Studio
  • AnythingLLM
  • Open WebUI
  • Msty
  • Cherry Studio
  • LibreChat
  • TypingMind
  • Chorus
  • 5ire
  • n8n
  • LangChain
  • LlamaIndex
  • CrewAI
  • Vercel AI SDK

Before you connect

Questions about OpenTelemetry Trace Analyzer.

The practical details behind the request, access and result.

Can the OpenTelemetry Trace Latency Analyzer help with microservices?

Yes, it is specifically designed for distributed traces. It helps you see how requests move between different services and where the time is being lost.

How do I find the slowest part of a trace using this Connector?

The Connector automatically identifies bottlenecks by looking for spans that exceed your time limits and highlighting the longest chains of dependencies.

Does it show how much time a service spends on its own work?

Yes, it calculates per-span self-time. This allows you to see if a service is actually slow or just waiting for a downstream response.

Can it help me find out why my API is slow?

Absolutely. By analyzing the trace spans, it identifies the critical path and provides a distribution of latency across your entire architecture.

What kind of data does the OpenTelemetry Trace Latency Analyzer need?

It requires OpenTelemetry-style trace data, specifically spans that include start and end timestamps along with parent-child IDs.

Does it work with multiple services at once?

Yes, it can analyze traces involving dozens of different services and give you a percentage-based breakdown of where the time is going.

What kind of trace data does this capability support?

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

How can I identify the slowest parts of my request?

By using identify_bottlenecks, you can find spans that exceed a specific latency threshold within your trace data.

Can I see how much time each service contributes to the total trace?

Yes, using get_service_distribution allows you to see an aggregation of average latency per service or span name.

One connection away

Give your agent a direct line to OpenTelemetry Trace Analyzer.

Connect OpenTelemetry Trace Analyzer once. Keep it beside 6,100+ managed Connectors when the next task needs more.

Explore every Connector No credit card required · Free tier available