Generate OpenTelemetry SDK configuration for distributed tracing, metrics, and logging across services.
You are an observability engineer specializing in OpenTelemetry. Generate complete instrumentation setup for a distributed system. ## Input Parameters - **Language**: [LANGUAGE] (Node.js / Python / .NET / Go / Java) - **Services**: [SERVICE_LIST] (comma-separated service names) - **Backend**: [OTEL_BACKEND] (Jaeger / Tempo / Datadog / New Relic) - **Collector Deployment**: [COLLECTOR] (sidecar / daemonset / gateway) - **Sampling Strategy**: [SAMPLING] (always / probabilistic / tail-based) ## Generate 1. **SDK initialization code** for each service: - TracerProvider with batch span processor - MeterProvider with periodic exporting reader - LoggerProvider with OTLP exporter - Resource attributes (service.name, service.version, deployment.environment) - Automatic instrumentation for HTTP, gRPC, database clients 2. **Collector configuration** (`otel-collector-config.yaml`): - Receivers: OTLP (gRPC + HTTP) - Processors: batch, memory_limiter, tail_sampling (if chosen), attributes - Exporters: configured backend + debug exporter for dev - Pipelines: traces, metrics, logs 3. **Sampling configuration** with the chosen strategy. 4. **Context propagation** setup (W3C TraceContext + Baggage). 5. **Custom span attributes** for business context. 6. **Kubernetes deployment** for the collector. ## Output Format Return initialization code per language, collector config YAML, and Kubernetes manifests. Include a diagram description of the telemetry flow.
Free to copy and use. Compatible with Claude 4 Opus, GPT-5, Gemini 2.5 Pro, Llama 4 Maverick.
List your services and their languages, choose your observability backend and collector deployment model. The prompt generates all SDK and collector configs.
Initial release
Sign in and download this prompt to leave a review.