observability-edot-java-migrate

To migrate from the Elastic APM agent to the EDOT Java agent, replace elastic-apm-agent.jar with elastic-otel-javaagent.jar and update your environment variables. This process requires defining precise configurations for agent attachment to ensure correct initialization.

Required environment variables for the EDOT Java agent dictate its initialization and attachment method. You must configure these variables precisely during migration to replace the classic Elastic APM agent and avoid misconfiguration.

No, running both agents simultaneously is disallowed. When migrating your Java application to the EDOT Java agent, you must remove the classic Elastic APM agent to prevent conflicts and ensure correct telemetry collection.

The best way to upgrade Java services across staging and production is to follow a reproducible migration checklist. This minimizes downtime and risk by validating telemetry and ensuring correct EDOT agent attachment and configuration.

Initialization failures after switching to the EDOT Java agent often stem from incorrect environment variables or conflicting agents. Ensure you remove the Elastic APM agent and apply the precise required attachment method during migration.