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.