Two weird exceptions while loading apm-agent 1.0.1 for java


(Carlos Cornejo) #1

Hi there,

My setup is:

  • ELK, APM, filebeat (all 6.5.0), apm-java-agent-1.0.1

  • wso2 api manager 2.5.0 (jdk 1.8.0_144)

    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.

apm-server.yml

apm-server:
  host: apm-server:8200
output:
  elasticsearch:
    hosts: http://elasticsearch:9200
    index: "apm-server-%{[beat.version]}-%{+yyyy.MM.dd}"
setup:
  kibana:
    host: "http://kibana:5601"
  dashboards:
    enabled: true
  template:
    enabled: false

wso2am docker-compose

...
wso2am:
  image: wso2am:2.5.0
  container_name: wso2am
  environment:
  - ELASTIC_APM_SERVICE_NAME=wso2am
  - ELASTIC_APM_SERVER_URLS=http://apm-server:8200
...

Any idea what is causing this?

Kind Regards,
Carlos M.


(Eyal Koren) #2

Hi,

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?

Thanks,
Eyal.


(Carlos Cornejo) #3

Hi Eyal,

Thanks for the super fast reply.

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??).

Will keep you posted if we see anything wrong.

You can close/solve the thread as you will.

Thanks again!
Carlos M.


(Eyal Koren) #4

Carlos,

Good luck!
We will be happy to get any feedback.

Thanks,
Eyal.