elastic/agent-observability-edot-java-migrate
> Migrate a Java application from the classic Elastic APM Java agent to the EDOT Java agent. Use when switching from elastic-apm-agent.jar to elastic-otel-javaagent.jar.
This is a copy. The original lives at elastic/observability-edot-java-migrate.
npx skills add https://github.com/elastic/agent-skills --skill observability-edot-java-migrate
Read the migration guide before making changes:
elastic-apm-agent.jar, elasticapm.properties, all ELASTIC_APM_* env vars,and any co.elastic.apm Maven/Gradle dependencies
elastic-otel-javaagent.jar (download fromMaven Central, not a Maven/Gradle
compile dependency)
-javaagent:/path/to/elastic-otel-javaagent.jar orJAVA_TOOL_OPTIONS="-javaagent:/path/to/elastic-otel-javaagent.jar" — without this the agent does nothing
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 / API_KEY)
OTEL_TRACES_EXPORTER, OTEL_METRICS_EXPORTER, or OTEL_LOGS_EXPORTER — the defaults are alreadycorrect
See the EDOT Java migration guide for
complete examples.
Take elastic/agent-observability-edot-java-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.