IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Metrics Logs »
Elastic Docs ›Elastic Observability [8.16] ›Application and service monitoring ›Application performance monitoring (APM) ›View and analyze data ›Drill down into application data

Infrastructure

edit
Infrastructure
edit

This functionality is in beta and is subject to change. The design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features.

The Infrastructure tab provides information about the containers, pods, and hosts that the selected service is linked to:

  • Pods: Uses the kubernetes.pod.name from the APM metrics data streams.
  • Containers: Uses the container.id from the APM metrics data streams.
  • Hosts: If the application is containerized—​if the APM metrics documents include container.id-- the host.name is used from the infrastructure data streams (filtered by container.id). If not, host.hostname is used from the APM metrics data streams.
Example view of the Infrastructure tab in Applications UI in Kibana

IT ops and software reliability engineers (SREs) can use this tab to quickly find a service’s underlying infrastructure resources when debugging a problem. Knowing what infrastructure is related to a service allows you to remediate issues by restarting, killing hanging instances, changing configuration, rolling back deployments, scaling up, scaling out, and so on.

Why is the infrastructure tab empty?

If there is no data in the Application UI’s infrastructure tab for a selected service, you can read more about why this happens and how to fix it in the troubleshooting docs.

« Metrics Logs »