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
Kibana version: 7.0.0
Elasticsearch version: 7.0.0
APM Server version: 7.0.1
APM Agent language and version: JAVA 1.7.0
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.
export CATALINA_OPTS="$CATALINA_OPTS -javaagent:/opt/apm/elastic-apm-agent-1.7.0.jar"
export CATALINA_OPTS="$CATALINA_OPTS -Delastic.apm.service_name=frm-service-des"
export CATALINA_OPTS="$CATALINA_OPTS -Delastic.apm.application_packages=com.example"
export CATALINA_OPTS="$CATALINA_OPTS -Delastic.apm.server_urls=http://localhost:8200"
export CATALINA_OPTS="$CATALINA_OPTS -Delastic.apm.environment=des"
export CATALINA_OPTS="$CATALINA_OPTS -Delastic.apm**.trace_methods**=com.example.app.service.job.*Job#execute"
Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):
Jobs are executed through Quartz threads, not tomcat threads. In kibana, I expected to also see jobs transactions, however I only see HTTP transactions (index_jsp#doGet).
Steps to reproduce:
- On tomcat, deploy a war application with Quartz jobs and try to trace them.
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
Jobs execution is viewed on logs:
INFO 2019-07-05 13:30:00,004 [scheduler_Worker-2] com.example.app.service.job.IntegrationJob - Job ** Integration_Job_Detail ** fired @ Fri Jul 05 13:30:00 CEST 2019
However no trace appears on APM.