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
TIP 1: select at least one tag that further categorizes your topic. For example
server for APM Server related questions,
java for questions regarding the Elastic APM Java agent, or
ui for questions about the APM App within Kibana.
TIP 2: Check out the troubleshooting guide first. Not only will it help you to resolve common problems faster but it also explains in more detail which information we need before we can properly help you.
Elasticsearch version: 7.9.2
APM Server version: 7.9.2
APM Agent language and version: java agent, version : 1.42.0
Browser version: Google chrom, Version 117.0.5938.92 (Official Build) (arm64)
Original install method (e.g. download page, yum, deb, from source, etc.) and version: Downloaded
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.
Nothing special about the setup. It is the standard setup as mentioned in the doc.
Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):
I have a Spring MVC application running on Google AppEngine with Java 17 as the runtime. I've configured it with the
-javaagent flag. My goal is to monitor and view all the requests and their associated spans in my application. However, I've encountered an issue where I can only see spans for some of the incoming requests. While I can see the overall execution time when filtering by trace IDs, I'm unable to view the specific spans related to those requests. I need assistance in understanding why this is happening and what steps I should take to ensure that I can view spans for all incoming requests.
The default setting for request tracing is to capture all incoming requests. However, I've explicitly set the
transaction_sample_rate to 1 to ensure that all requests are sampled for tracing. Surprisingly, even with this configuration, I'm still unable to capture traces for all requests.
These are the configs that I have used:
-javaagent:WEB-INF/lib/elastic-apm-agent-1.42.0.jar -Delastic.apm.service_name=myApp -Delastic.apm.environment=staging -Delastic.apm.server_urls=http://xx.yy.zz.aa:8200 -Delastic.apm.secret_token=******* -Delastic.apm.application_packages=com.hanok -Delastic.apm.trace_methods=com.hanok.*
This is the expected result where I could see all the spans:
Steps to reproduce:
1.Deploy the app using Java agent configs
2.Try filtering out using a trace.id
3.This is what I get as the result which does not have spans at all :
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):