distributed-tracing

Implement distributed tracing with Jaeger and Tempo for microservices.

1|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/tense-i/tslink --skill distributed-tracing-tense-i
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: distributed-tracing
Source: https://github.com/tense-i/tslink/tree/main/skills/distributed-tracing
Command: npx skills add https://github.com/tense-i/tslink --skill distributed-tracing-tense-i

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides deep visibility into the flow of requests across distributed microservices, enabling quick identification of performance bottlenecks and error sources.

Core Features & Use Cases

  • End-to-end Request Tracking: Follow a single request as it travels through multiple services.
  • Performance Bottleneck Identification: Pinpoint which service or operation is causing latency.
  • Error Propagation Analysis: Understand how and where errors originate and spread.
  • Observability Enhancement: Integrate tracing into your microservice architecture for better debugging and monitoring.
  • Use Case: Debugging a slow API response by tracing its path from the frontend through authentication, user service, and database calls to find the exact point of delay.

Quick Start

Use the distributed-tracing skill to implement tracing in a Python Flask application using OpenTelemetry and Jaeger.

Frequently Asked Questions about distributed-tracing

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

FAQPage Schema
How do I trace requests across microservices to find performance bottlenecks?

Distributed tracing tracks requests across microservices to pinpoint the exact service or operation causing latency. By following a request's path end-to-end, it identifies performance bottlenecks and analyzes dependencies for observability.

How does OpenTelemetry instrumentation work with Jaeger and Tempo?

OpenTelemetry provides application instrumentation and context propagation via HTTP headers for distributed tracing. The generated trace data is then collected and visualized using backends like Jaeger and Tempo to analyze request flows.

What is the best way to debug a slow API response in a microservice architecture?

The best way to debug a slow API response is using distributed tracing to trace its path from the frontend through authentication, user service, and database calls. This reveals the exact point of delay across the microservices.

Can I implement distributed tracing in a Python Flask application?

Yes, you can implement distributed tracing in a Python Flask application. The skill provides a quick start approach using OpenTelemetry for application instrumentation and Jaeger as the tracing backend to monitor request flows.

Does distributed tracing help with error propagation analysis in microservices?

Distributed tracing helps with error propagation analysis by tracking how and where errors originate and spread across microservices. It provides deep visibility into the flow of requests to quickly identify error sources.