# APM - Infrastructure Tab not working for any apm agent **URL:** \ **Category:** APM\ **Tags:** ui\ **Created:** [April 30, 2025, 7:07pm UTC](https://discuss.elastic.co/t/apm-infrastructure-tab-not-working-for-any-apm-agent/377687 "2025-04-30T19:07:28Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![erikg](https://avatars.discourse-cdn.com/v4/letter/e/91b2a8/32.png) [@erikg](https://discuss.elastic.co/u/erikg)\ **Post date:** [April 30, 2025, 7:07pm UTC](https://discuss.elastic.co/t/apm-infrastructure-tab-not-working-for-any-apm-agent/377687/1 "2025-04-30T19:07:28Z")
**Kibana version** : 8.18.0 **Elasticsearch version** : 8.18.0 **APM Server version** : 8.18.0 **APM Agent language and version** : Python/Java/.NET latest 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 **Description of the problem including expected versus actual behavior. Please include screenshots (if relevant)**: ![image](https://us1.discourse-cdn.com/elastic/original/3X/c/4/c4e5b9712eccbee47cea6f9aad0eb8f8f89810cb.png) **Steps to reproduce** : 1. Add service to APM 2. Click on Infrastructure Tab **Errors in browser console (if relevant)**: No errors **Provide logs and/or server output (if relevant)**: ---
**Author:** ![Rafa\_Silva](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rafa_silva/32/147814_2.png) [@Rafa\_Silva](https://discuss.elastic.co/u/Rafa_Silva)\ **Post date:** [May 3, 2025, 3:37am UTC](https://discuss.elastic.co/t/apm-infrastructure-tab-not-working-for-any-apm-agent/377687/2 "2025-05-03T03:37:46Z")
If your APM Infrastructure tab is showing up blank and you’re not seeing any errors, here are a few things that could be going on — I’ve run into this myself before: Missing metadata – Check if fields like host.name, container.id, or kubernetes.pod.name are showing up in your APM data (you can check that in Discover). These are key for linking your services to the infrastructure view. No metric data – The Infrastructure tab depends on system or container metrics coming from something like the Elastic Agent, Metricbeat, or the OpenTelemetry Collector. Make sure the metrics-\* indices exist and have fresh data in them. Missing service.node.name – Some parts of the APM UI rely on this field being present. You can configure it in the APM agent — for example, with elastic.apm.service\_node\_name in Java. No link between APM and metrics – Even if both APM and metrics are being collected, if the identifiers (like hostnames) don’t match up, the tab might not show anything. What to do: Make sure you have system metrics being collected — deploy Elastic Agent or Metricbeat on the same host running your service. Ensure your APM agent is sending both host.name and service.node.name. Double-check that data is coming into both apm-\* and metrics-\* indices. ---
**Author:** ![jlhieselaar](https://avatars.discourse-cdn.com/v4/letter/j/ed655f/32.png) [@jlhieselaar](https://discuss.elastic.co/u/jlhieselaar)\ **Post date:** [November 4, 2025, 10:02am UTC](https://discuss.elastic.co/t/apm-infrastructure-tab-not-working-for-any-apm-agent/377687/3 "2025-11-04T10:02:28Z")
Hello there, I have the same problem I do not see data in the infrastructure tab of the APM APP - both apm data and infrastructure data contain the exact same host.hostname and host.name - [I do see the data in the Infrastructure inventory](https://www.elastic.co/docs/troubleshoot/observability/apm/common-problems#troubleshooting-apm-infra-data), also the host overview shows direct links to the services that run on the hosts I’m using: - Elastic Cloud 9.2.0 - Metricbeat 9.2.0 for default system metrics installed on the Node - Elastic-agent 9.2.0 with a kubernetes integration with kubelet, apiserver and kube-state-metrics fully enabled - Java apm-agents 1.54 on 4 java test apps in K8s, service.node.name is auto-set to container.id - K8s deployment manifest has env vars for enabling metadata: [Elastic APM events intake API | Elastic Docs](https://www.elastic.co/docs/solutions/observability/apm/elastic-apm-events-intake-api#apm-api-kubernetes-data) - I tested with the system integration on the elastic-agent 9.2.0 instead of metricbeat 9.2.0: no difference Confusing is this table from [Elastic APM events intake API | Elastic Docs](https://www.elastic.co/docs/solutions/observability/apm/elastic-apm-events-intake-api#apm-api-kubernetes-data): | **Environment variable** | **Metadata field name** | | --- | --- | | `KUBERNETES_NODE_NAME` | system.kubernetes.node.name | | `KUBERNETES_POD_NAME` | system.kubernetes.pod.name | | `KUBERNETES_NAMESPACE` | system.kubernetes.namespace | | `KUBERNETES_POD_UID` | system.kubernetes.pod.uid | → In my apm-traces and apm-metrics documents the values of the fields above end up in different fields, namely: | **Environment variable** | **Metadata field name** | | --- | --- | | `KUBERNETES_NODE_NAME` | kubernetes.node.name | | `KUBERNETES_POD_NAME` | kubernetes.pod.name | | `KUBERNETES_NAMESPACE` | kubernetes.namespace | | `KUBERNETES_POD_UID` | kubernetes.pod.uid | Could this be the reason of the infrastructure tab not working?