But it looks like GitHub - elastic/elastic-otel-java doesn't have an environment variable or system property like elastic.apm.application_packages? Is this expected behavior? This is how I tested the Elastic Distribution of OpenTelemetry Java:
I don't think this requires any reproducible git, because at this point the Elastic Distribution of OpenTelemetry Java is instrumenting io.opentelemetry.apache-httpclient-5.0 .
Something like the elastic.apm.application_packages system property for the Elastic APM Java Agent does seem to work. But I can't find an equivalent for the Elastic Distribution of OpenTelemetry Java.
I think you are referring to the "Framework" description in the dropdown about the service from the Java icon. This gets set by the service.framework.name attribute which the agent generates from the instrumentation. The Elastic APM Java Agent has carefully assigned names for these values which are different and more readably descriptive than the name of the instrumentation (here spring-mvc) that generates the traces.
The Elastic Distribution of OpenTelemetry Java (EDOT Java) uses the logic of the upstream OpenTelemetry Java agent, which doesn't have equivalent readably descriptive naming for instrumentations, which means only the instrumentation name itself can be shown.
None of this is related to application_packages.
So for now, there is no mechanism to display a nicer descriptive name in the "Framework" when using the EDOT Java agent. I've opened an enhancement request for this
The Elastic APM Java Agent startup time can be improved a number of ways. The EDOT Java agent doesn't (yet) have as much flexibility. The referred to issue will not improve startup time, it will only improve display of traces in the trace waterfall diagram
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.