Basically we use apm-java-agent in wso2am and it seems to be working fine connection wise, but we can see two weird exceptions in the wso2am logs exception-trace-1 and exception-trace-2.
Thanks for trying it out!
These Exceptions are thrown during the process of agent trying to figure out which classes should be instrument among all loaded classes- it fails to locate some dependencies in classpath. It shouldn't be a problem for your application. In some cases, such failures may mean that the agent will fail to instrument something it should, but that doesn't seem to be the case here.
Are you experiencing any problems with your application?
Are you getting what you expect to get in the APM console?
TBHWY we're starting with the product and we're not just yet there to miss out some metrics but so far it seems to be working fine.
We BTW are not just yet defining which classes should be monitored via the ELASTIC_APM_APPLICATION_PACKAGES env property (which according to the doc should apply to all??).
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.