Using the Infrastructure appedit

Use the Infrastructure app in Kibana to monitor your infrastructure and identify problems in real time. You can explore metrics for hosts, containers, and services. You can also drill down to view more detailed metrics, or seamlessly switch to view the corresponding logs, application traces, and uptime information.

Initially, the Inventory tab shows an overview of the hosts in of your infrastructure and the current CPU usage for each host. From here, you can drill down into areas of interest.

Infrastructure Overview in Kibana

Choose the high-level view of your infrastructureedit

Select the high-level view from Hosts, Kubernetes, or Docker. When you change views, you see the same data through the perspective of a different category.

The default representation is the Map view, which shows your components in a waffle map of one or more rectangular grids. If the view you select has a large number of components, you can hover over a component to see the details for that component. Alternatively, if you would prefer to see your infrastructure as a table, click Table view.

Select the metric to viewedit

Select the metric to view from the Metric dropdown list. The available metrics are those that are most relevant for the high-level view you selected.

Group componentsedit

Select the way you want to group the infrastructure components from the Group By dropdown list. The available options are specific to your physical, virtual, or container-based infrastructure. Examples of grouping options include Availability Zone, Machine Type, Project ID, and Cloud Provider for hosts, and Namespace and Node for Kubernetes.

Use the power of searchedit

Use the search bar to perform ad hoc or structured searches using Kibana Query Language which features autocomplete and a simple, easy to use syntax. For example, enter host.hostname : "host1" to see only the information for host1.

Specify the time and dateedit

Click the time selector to choose the timeframe for the metrics. The values shown are the values for the last minute at the specified time and date.

Auto-refresh metricsedit

Select Auto-refresh to keep up-to-date metrics information coming in, or Stop refreshing to focus on historical data without new distractions.

Configure the data to use for your metricsedit

The default source configuration for metrics is specified in the Infrastructure app settings in the Kibana configuration file. The default configuration uses the metricbeat-* index pattern to query the data. The default configuration also defines field settings for things like timestamps and container names.

If your metrics have custom index patterns, or use non-default field settings, you can override the default settings. Click Configuration to change the settings. This opens the Configure source fly-out dialog.

Note

These settings are shared with logs. Changes you make here may also affect the settings used in the Logs tab.

In the Configure source dialog, you can change the following values:

  • Name: the name of the source configuration
  • Indices: the index pattern or patterns in the Elasticsearch indices to read metrics data and log data from
  • Fields: the names of specific fields in the indices that need are used to query and interpret the data correctly
Tip

If Spaces are enabled in your Kibana instance, any configuration changes you make here are specific to the current space. You can make different subsets of data available by creating multiple spaces with different data source configurations.

Tip

If you don’t see the Configuration option, you may not have sufficient privileges to change the source configuration. For more information see Granting access to Kibana.

Visualize multiple metrics in Metrics Exploreredit

Metrics Explorer allows you to visualize and analyze metrics for multiple components in a powerful and configurable way. Click the Metrics Explorer tab to get started.

Drill down for related informationedit

Hover over a component to see more information about that component.

Click a component to see the other actions available for that component. You can:

Depending on the features you have installed and configured, you may also be able to: