分布式追踪与关联ID实现指南 - 微服务调试与性能监控最佳实践

correlation-tracing by aj-geddes/useful-ai-prompts

145 周安装量

161 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill correlation-tracing

微服务架构性能优化分布式系统

🇨🇳中文介绍

关联与分布式追踪

概述

实现关联 ID 和分布式追踪，以跨多个服务跟踪请求并理解系统行为。

使用场景

微服务架构
调试分布式系统
性能监控
请求流可视化
跨服务错误追踪
依赖关系分析
延迟优化

快速开始

最小工作示例：

import express from "express";
import { v4 as uuidv4 } from "uuid";

// 用于上下文的异步本地存储
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,
  ) => {
    // 提取或生成追踪 ID
    const traceId = (req.headers["x-trace-id"] as string) || uuidv4();
    const parentSpanId = req.headers["x-span-id"] as string;
    const spanId = uuidv4();
// ... (完整实现请参阅参考指南)

参考指南

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

指南	内容
关联 ID 中间件 (Express)	关联 ID 中间件 (Express)
OpenTelemetry 集成	OpenTelemetry 集成
Python 分布式追踪	Python 分布式追踪
手动追踪传播	手动追踪传播

🇺🇸English

Correlation & Distributed Tracing

Overview
When to Use
Quick Start
Reference Guides
Best Practices

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

Weekly Installs

110

Repository

aj-geddes/usefu…-prompts

GitHub Stars

121

First Seen

Jan 21, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

opencode93

gemini-cli91

codex87

cursor85

claude-code83

github-copilot75