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.6.0
Elasticsearch version: 7.6.0
APM Server version: 7.6.0
APM Agent language and version: 1.2.0
Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):
I have set up an elastic stack with elasticsearch, filebeat, kibana and apm server, and an spring-boot-application with the apm java agent and started my setup in a docker compose file. I have enabled the dashboard and I can see traces about processes in the application. But I cannot filter for container id, because there is no id. How do I enable my stack apm server/apm agent to receive the metadata about container id, pod id and so on.
Where can I enable metadata for apm server / apm agent to receive the container id for instance.
@felixbarny
One more question: I receive the container id but the pod is still missing. What settings do I need to adjust to get the information about pods?
Right now I setup this https://www.elastic.co/de/blog/using-elastic-apm-java-agent-on-kubernetes-k8s blogpost. And its working properly for APM Server in general and the container id specificly. If I chose the petclinic service I've got no information about pods. Can I even expect to see pods in this setup?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.