Kibana version: 8.7.0
Elasticsearch version: 8.7.0
APM Server version: 8.7.0
APM Agent language and version: 1.36.0
I just started using
log_sending=true in the Java agent on one of our Q-Systems. The logs are transferred and stored in Elastic just fine. I can search the logs manually in Discover and everything, it is just that the logs are NOT shown in the APM UI.
This seems to be caused by the fact that we do not have microservices - we are running multiple applications in a single tomcat instance. Let's say I have an application called
MyApplication running, I would expect the
service.name of all logs to be set to
MyApplication. In reality, the agent seems to instrument the logback appenders and has no reference to the original application (
event.dataset is set to
tomcat-application). This means, calling
https://my-kibana-host:5601/s/my-team/app/apm/services/MyApplication/logs does not show the application logs.
I would prefer that the Elastic Agent would send the logs with the correct service name to make correlation easier.