otel-instrument

You can add OpenTelemetry tracing and metrics by applying official SDK auto-instrumentation to your existing application entrypoint, which generates HTTP server spans and request-duration metrics without requiring large code refactors.

To avoid duplicate OpenTelemetry SDK initialization, perform an evidence-first preflight check to detect existing SDK initialization, then safely apply auto-instrumentation that reuses the existing runtime entrypoint instead of creating a new one.

Yes, you can add custom OpenTelemetry spans for specific business operations after auto-instrumentation is confirmed, applying explicit error-status behavior so APM backends can accurately track targeted business signals.

Yes, OpenTelemetry auto-instrumentation supports Python, Node.js, Java, and Go services by applying the appropriate language-specific official SDKs and libraries to automatically wire up tracing and HTTP server telemetry.

You configure OTLP export and service identity for OpenTelemetry instrumentation by setting standard environment variables, ensuring the service.name and export endpoints are defined without hardcoding values into the application logic.

HTTP request-duration metrics may not appear if the OpenTelemetry setup lacks the recommended HTTP server wrapping, which is required to ensure HTTP server telemetry includes validation-ready request-duration metrics alongside traces.