correlation-tracing▌
aj-geddes/useful-ai-prompts · updated Apr 8, 2026
Implement correlation IDs and distributed tracing to track requests across multiple services and understand system behavior.
Correlation & Distributed Tracing
Table of Contents
Overview
Implement correlation IDs and distributed tracing to track requests across multiple services and understand system behavior.
When to Use
- Microservices architectures
- Debugging distributed systems
- Performance monitoring
- Request flow visualization
- Error tracking across services
- Dependency analysis
- Latency optimization
Quick Start
Minimal working example:
import express from "express";
import { v4 as uuidv4 } from "uuid";
// Async local storage for context
import { AsyncLocalStorage } from "async_hooks";
const traceContext = new AsyncLocalStorage<Map<string, any>>();
interface TraceContext {
traceId: string;
spanId: string;
parentSpanId?: string;
serviceName: string;
}
function correlationMiddleware(serviceName: string) {
return (
req: express.Request,
res: express.Response,
next: express.NextFunction,
) => {
// Extract or generate trace ID
const traceId = (req.headers["x-trace-id"] as string) || uuidv4();
const parentSpanId = req.headers["x-span-id"] as string;
const spanId = uuidv4();
// ... (see reference guides for full implementation)
Reference Guides
Detailed implementations in the references/ directory:
| Guide | Contents |
|---|---|
| Correlation ID Middleware (Express) | Correlation ID Middleware (Express) |
| OpenTelemetry Integration | OpenTelemetry Integration |
| Python Distributed Tracing | Python Distributed Tracing |
| Manual Trace Propagation | Manual Trace Propagation |
Best Practices
✅ DO
- Generate trace IDs at entry points
- Propagate trace context across services
- Include correlation IDs in logs
- Use structured logging
- Set appropriate span attributes
- Sample traces in high-traffic systems
- Monitor trace collection overhead
- Implement context propagation
❌ DON'T
- Skip trace propagation
- Log without correlation context
- Create too many spans
- Store sensitive data in spans
- Block on trace reporting
- Forget error tracking
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★33 reviews- ★★★★★Ganesh Mohane· Dec 28, 2024
Solid pick for teams standardizing on skills: correlation-tracing is focused, and the summary matches what you get after install.
- ★★★★★Kiara Srinivasan· Dec 16, 2024
correlation-tracing has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Sakshi Patil· Nov 19, 2024
We added correlation-tracing from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Kaira Lopez· Nov 7, 2024
correlation-tracing fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Hana Brown· Oct 26, 2024
We added correlation-tracing from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Chaitanya Patil· Oct 10, 2024
correlation-tracing fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Maya Robinson· Sep 17, 2024
correlation-tracing reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Ama Reddy· Sep 17, 2024
I recommend correlation-tracing for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Piyush G· Sep 1, 2024
Registry listing for correlation-tracing matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Shikha Mishra· Aug 20, 2024
correlation-tracing reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 33