otel-python

OpenTelemetry traces and metrics often fail to appear due to SDK initialization or instrumentation ordering issues. This Skill audits your Python service to repair cross-signal correctness, ensuring telemetry reliably correlates and shows up with correct service identity.

Setting up OpenTelemetry instrumentation for Flask, Django, and FastAPI requires framework-aware guidance for exporter configuration and context propagation. This Skill applies correct SDK initialization and instrumentation ordering tailored to your confirmed Python codebase.

Python OpenTelemetry logs fail to correlate with traces due to common cross-signal pitfalls in resource attributes and context propagation. This Skill checks cross-signal correctness to fix missing or non-correlated telemetry across traces, metrics, and logs.

Yes, OpenTelemetry Python setup supports Celery and async workers. This Skill applies instrumentation and cross-signal correctness checks to confirmed async worker codebases, ensuring traces, metrics, and logs propagate correctly across these environments.

You can safely audit Python OpenTelemetry SDK configuration because an operational safety gate requires a proposed diff and explicit user confirmation before applying any changes. This prevents unexpected source file mutations during instrumentation repairs.