elastic/agent-observability-edot-python-migrate
> Migrate a Python application from the classic Elastic APM Python agent to the EDOT Python agent. Use when switching from elastic-apm to elastic-opentelemetry.
This is a copy. The original lives at elastic/observability-edot-python-migrate.
npx skills add https://github.com/elastic/agent-skills --skill observability-edot-python-migrate
Read the migration guide before making changes:
elastic-apm from requirements, ElasticAPM(app) / elasticapm.contrib.* fromapplication code, app.config['ELASTIC_APM'] blocks, and all ELASTIC_APM_* env vars
elastic-opentelemetry via pip (add to requirements.txt or equivalent)edot-bootstrap --action=install during image build to install auto-instrumentation packages for detectedlibraries
opentelemetry-instrument — e.g. opentelemetry-instrument gunicorn app:app.Without this, no telemetry is collected
OTEL_SERVICE_NAME (replaces ELASTIC_APM_SERVICE_NAME)OTEL_EXPORTER_OTLP_ENDPOINT — must be the managed OTLP endpoint or EDOT Collector URL. Do NOT reuse theold ELASTIC_APM_SERVER_URL value. Never use an APM Server URL (no apm-server, no :8200, no
/intake/v2/events)
OTEL_EXPORTER_OTLP_HEADERS — "Authorization=ApiKey <key>" or "Authorization=Bearer <token>" (replacesELASTIC_APM_SECRET_TOKEN)
OTEL_TRACES_EXPORTER, OTEL_METRICS_EXPORTER, or OTEL_LOGS_EXPORTER — the defaults are alreadycorrect
elastic-apm and EDOT on the same applicationSee the EDOT Python migration guide
for complete examples.
Take elastic/agent-observability-edot-python-migrate from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.