prompt

Distributed Tracing Setup Guide

Configure distributed tracing (OpenTelemetry/Jaeger) with instrumentation boilerplate for services.

Updated June 2026
The prompt
Create a distributed tracing setup for a {{arch_style}} system with {{num_services}} services:
{{service_list}}

Requirements:
- Tracing backend: {{tracing_backend}}
- Framework: {{framework}}
- Sampling strategy: {{sampling_rate}}
- Trace storage: {{storage}}
- Team expertise: {{team_level}}

Provide:
1. Architecture diagram (service spans hierarchy)
2. Instrumentation boilerplate per service type
3. Custom span injection rules ({{business_context}})
4. Sampling & retention policy
5. Debugging workflow (query examples)
Did it work? Rate this prompt

Variables

Architecture (microservices/monolith/hybrid)
Number of services
Service names & techs (e.g., auth-api:Node, payment-svc:Go)
Backend (Jaeger/DataDog/Lightstep)
Instrumentation library (OTel/etc)
Sampling rate (e.g., 10% or adaptive)
Storage backend
Team DevOps expertise
Business context to trace (e.g., user_id, tenant)

Details

Author

AI Khazna

License

Security

Type

prompt

Related assets

More curated picks in Development & Code.

Audit before you install

Run any source through our checks - AI visibility, security, performance, and stack detection.

More in Development & Code