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.
Kibana version: 6.8.5
Elasticsearch version: 6.8.5
APM Server version: 6.8.11
APM Agent language and version: 1.19.0
Browser version: Vivaldi 3.5.2115.81
Original install method (e.g. download page, yum, deb, from source, etc.) and version: install from docker hub, versions are above
Fresh install or upgraded from other version? Fresh
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.
I am using nomad for orchestration (it's basically like kubernetes) of my services written in java and using spring boot. It's all running in docker containers, the apm server is running there, too. The logs of the containers are automatically shipped to ES using filebeat.
Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):
I have custom application errors. These include technical errors like no database connection or other services not available. There are also functional errors, like data problems in the database, false formatting and other things.
I installed elastic apm and really like the graphical representation in Kibana. It works fine, I can see detailed information e.g. for REST endpoints that are called in my services, how long things take etc.
What I would also like to see is the errors of my services in the errors tab. Currently I only have one error in the errors tab which is an internal exception that my service didn't catch by itself. However all the errors that were generated by the application are not visible.
But I would really like to see them there, since the UI provides some really nice features that I want to use in the future to get a better overview of the errors.
The errors are created in the line
and I can see them in the application log index in ES, so they get transferred without a problem. But the apm agent doesn't seem to see them as an error, so I can't find them in Kibana.
Steps to reproduce:
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):