Hey, I have a question regarding experimental automatic set up java agent methods.
What does in this case experimental mean? Is it safe to use it on production (bug free and stable) or it just could be replaced/deleted in future?
This is not going to be replaced. We have plans to make this work for OSGi and similar environments in the future, but that requires some refactoring.
See also the caveats section for more details what's not working: https://www.elastic.co/guide/en/apm/agent/java/1.x/setup-attach-cli.html#setup-attach-cli-caveats
As a rule of thumb: if it's working for your server (you don't see a wall of exceptions), there's no difference in stability compared to the regular setup.
You might be able to work around those exceptions with some manual OSGi configuration:
Where to add this varies based on the server and OSGi container. For some, there is already a file which already includes a list of packages. So search for
bootdelegation in your server directory and add
co.elastic.apm.agent.* to the existing list.
Thanks for fast response! Ok will give it a try
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.