--- name: setting-up-distributed-tracing-f2c81101946c description: 'Execute this skill automates the setup of distributed tracing for microservices. it helps developers implement end-to-end request visibility by configuring context propagation, span creation, trace collection, and analysis. use this skill when the user re... Use when appropriate context detected. Trigger with relevant phrases based on skill purpose. ' allowed-tools: Read, Write, Edit, Grep, Glob, Bash(cmd:*) version: 1.22.0 author: Jeremy Longshore license: MIT tags: - performance - microservices - tracing compatibility: Designed for Claude Code --- # Distributed Tracing Setup Set up distributed tracing for microservices using OpenTelemetry, Jaeger, or Zipkin with context propagation, span creation, and trace collection configuration. ## Overview This skill streamlines the process of setting up distributed tracing in a microservices environment. It guides you through the key steps of instrumenting your services, configuring trace context propagation, and selecting a backend for trace collection and analysis, enabling comprehensive monitoring and debugging. ## How It Works 1. **Backend Selection**: Determines the preferred tracing backend (e.g., Jaeger, Zipkin, Datadog). 2. **Instrumentation Strategy**: Designs an instrumentation strategy for each service, focusing on key operations and dependencies. 3. **Configuration Generation**: Generates the necessary configuration files and code snippets to enable distributed tracing. ## When to Use This Skill This skill activates when you need to: - Implement distributed tracing in a microservices application. - Gain end-to-end visibility into request flows across multiple services. - Troubleshoot performance bottlenecks and latency issues. ## Examples ### Example 1: Adding Tracing to a New Microservice User request: "setup tracing for the new payment service" The skill will: 1. Prompt for the preferred tracing backend (e.g., Jaeger). 2. Generate code snippets for OpenTelemetry instrumentation in the payment service. ### Example 2: Troubleshooting Performance Issues User request: "implement distributed tracing to debug slow checkout process" The skill will: 1. Guide the user through instrumenting relevant services in the checkout flow. 2. Provide configuration examples for context propagation. ## Best Practices - **Backend Choice**: Select a tracing backend that aligns with your existing infrastructure and monitoring tools. - **Sampling Strategy**: Implement a sampling strategy to manage trace volume and cost, especially in high-traffic environments. - **Context Propagation**: Ensure proper context propagation across all services to maintain trace continuity. ## Integration This skill can be used in conjunction with other plugins to automate the deployment and configuration of tracing infrastructure. For example, it can integrate with infrastructure-as-code tools to provision Jaeger or Zipkin clusters. ## Prerequisites - Appropriate file access permissions - Required dependencies installed ## Instructions 1. Invoke this skill when the trigger conditions are met 2. Provide necessary context and parameters 3. Review the generated output 4. Apply modifications as needed ## Output The skill produces structured output relevant to the task. ## Error Handling - Invalid input: Prompts for correction - Missing dependencies: Lists required components - Permission errors: Suggests remediation steps ## Resources - Project documentation - Related skills and commands --- Source attribution: jeremylongshore Original project: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/ab85a061f7bcc039dac13ee193de7a4cd4388571/plugins/performance/distributed-tracing-setup/skills/setting-up-distributed-tracing/SKILL.md License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Dave AI. ## Upstream license notice MIT License Copyright (c) 2026 Claude Code Plugins Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Dave AI resource metadata Creator / publisher: jeremylongshore Original project: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/ab85a061f7bcc039dac13ee193de7a4cd4388571/plugins/performance/distributed-tracing-setup/skills/setting-up-distributed-tracing/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering Roles: Backend Developer, Data Engineer, DevOps / SRE Specialties: Backend, Design, DevOps, Word Documents, Frontend, Playwright, Stripe Tools: Datadog, Jaeger, Zipkin Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: b3f8e9c3d54df3d776c6e51da0612b27d83abd80b8207335fb2e6b22f66d2e37