Setting up APM agent on Spring Application with War File Deployment to Tomcat

If you are asking about a problem you are experiencing, please use the following template, as it will help us help you. If you have a different problem, please delete all of this text :slight_smile:

Kibana version:
Version: 6.2.4
Elasticsearch version:
Version: 6.2.4
APM Server version:
APM Agent language and version:
Browser version:
Chrome latest
Original install method (e.g. download page, yum, deb, from source, etc.) and version:

Fresh install or upgraded from other version?

Is there anything special in your setup? For example, are you using the Logstash or Kafka outputs? Are you using a load balancer in front of the APM Servers? Have you changed index pattern, generated custom templates, changed agent configuration etc.

Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):

I could not locate in documentation clear steps to attach amp agent to java application that does not consist of main entry point eg. mvc spring maven project that uses war file to deploy to tomcat server. Also if there are examples of implementation of using the Public api also available.


Hi :wave:

check this out:


This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.