APM - Infrastructure Tab not working for any apm agent

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):

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):

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.

1 Like