observability-edot-python-migrate

To migrate from Elastic APM to OpenTelemetry, remove all elastic-apm references from your code and environment, then install the elastic-opentelemetry package and bootstrap auto-instrumentation to collect telemetry data.

Switching to EDOT Python instrumentation requires replacing classic Elastic APM environment variables with exact EDOT OpenTelemetry configurations to ensure telemetry is collected properly across your runtime environments.

OpenTelemetry auto-instrumentation bootstrap for Python works by wrapping your application entrypoint and installing instrumentation libraries automatically, ensuring telemetry is collected across typical Python services without manual code changes.

Yes, Elastic EDOT supports typical Python services and deployment environments by guiding exact dependency updates, bootstrap tooling, and entrypoint wrapping to ensure telemetry is collected across your existing infrastructure.

Python telemetry is not collected after migrating if the application entrypoint is not properly wrapped or if exact EDOT environment variables and bootstrap tooling steps were not followed during the OpenTelemetry migration.

The difference between Elastic APM and EDOT is that EDOT uses OpenTelemetry standards, requiring the removal of classic elastic-apm references and installation of elastic-opentelemetry to continue telemetry collection natively.