Kibana version: 6.5.4
Elasticsearch version: 6.5.4
APM Server version: 6.5.4
APM Agent language and version: java 1.3.0
APM Agent configuration:
active=true instrument=true environment=[redacted] service_name=[redacted] service_version=1.2 transaction_sample_rate=1.0 transaction_max_spans=1000 disable_instrumentations= capture_body=all capture_headers=true log_level=INFO enable_log_correlation=true secret_token=[redacted] server_urls=[redacted] verify_server_cert=true flush_interval=1s max_queue_size=1024 application_packages=[redacted] stack_trace_limit=50 trace_methods=
Browser version: Chrome 72
Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):
We are using APM Java Agent to monitor performance of our Tomcat based applications. This works fine for most usecases but in one application I instrumented the startup by annotating the init-method of the central class and Kibana does not show the Spans - only the transaction.
When I use "View transaction in discover" however, if I click on the "View Spans" link of the transaction.id I see a lot of Spans. Some Spans are from the annotation @CaptureSpan but the majority are Spans created from SQLs.
What is confusing to me: I have set transaction_max_spans to 1000 but Discovery shows me 12k of Spans. Can this be the root cause of Kibana not showing any Spans?