jaeger

Deploy and configure Jaeger to store, index, and visualize KYC tracing spans.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/pohlai88/AFENDA --skill jaeger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jaeger
Source: https://github.com/pohlai88/AFENDA/tree/main/.agents/skills/jaeger
Command: npx skills add https://github.com/pohlai88/AFENDA --skill jaeger

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the need for robust observability in the KYC verification pipeline by deploying and configuring Jaeger for distributed tracing. It enables the storage, indexing, and visualization of spans, providing deep insights into the entire verification flow.

Core Features & Use Cases

  • Jaeger Deployment: Facilitates the setup of Jaeger, either as a self-hosted all-in-one solution for development or a distributed setup with Elasticsearch for production.
  • Trace Visualization: Allows users to visualize the complete flow of a KYC verification, identifying latency and bottlenecks across microservices.
  • Observability Enhancement: Integrates with OpenTelemetry Collector to process and route traces from KYC services to Jaeger.
  • Use Case: When a KYC verification process is experiencing unexpected delays, this Skill can be used to deploy Jaeger, collect traces from all involved services, and then visualize the trace waterfall to pinpoint which specific microservice is causing the slowdown.

Quick Start

Deploy Jaeger using the provided docker-compose.yml for development environments.

Frequently Asked Questions about jaeger

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

FAQPage Schema
How do I set up distributed tracing for a KYC verification pipeline?

To set up distributed tracing for a KYC verification pipeline, deploy and configure Jaeger as the tracing backend to store, index, and visualize spans from your microservices. This enables you to analyze the complete verification flow.

Why does my KYC verification process have unexpected latency across microservices?

Unexpected KYC verification latency can be pinpointed by visualizing the trace waterfall in Jaeger. Collecting spans from all involved microservices helps you identify exactly which specific service is causing the slowdown.

How do I deploy Jaeger for backend observability in development versus production?

For backend observability, deploy Jaeger as a self-hosted all-in-one solution for development environments using docker-compose, or configure a distributed setup with Elasticsearch for production to store and index traces.

Can I use OpenTelemetry Collector to route traces to Jaeger?

Yes, you can integrate the OpenTelemetry Collector to process and route traces from your KYC services to Jaeger. This setup separates the Jaeger infrastructure from the OpenTelemetry SDK instrumentation.

What is the best way to monitor bottlenecks in a KYC flow from selfie capture to final decision?

The best way to monitor bottlenecks in a KYC flow from selfie capture to final decision is to use Jaeger distributed tracing. It visualizes the complete verification flow, allowing you to identify latency issues across microservices.

Does Jaeger distributed tracing require Elasticsearch for trace storage?

Jaeger distributed tracing does not strictly require Elasticsearch for trace storage. While Elasticsearch is recommended for a distributed production setup, you can use a self-hosted all-in-one solution for development environments.