diff --git a/reference/observability/observability-aws-metrics.md b/reference/observability/observability-aws-metrics.md index f729e64c05..b72b8e6fdd 100644 --- a/reference/observability/observability-aws-metrics.md +++ b/reference/observability/observability-aws-metrics.md @@ -2,6 +2,9 @@ mapped_pages: - https://www.elastic.co/guide/en/serverless/current/observability-aws-metrics.html - https://www.elastic.co/guide/en/observability/current/aws-metrics.html +applies_to: + stack: ga + serverless: ga products: - id: cloud-serverless - id: observability @@ -14,12 +17,28 @@ Additional AWS charges for GetMetricData API requests are generated using this m :::: - - ## Monitor EC2 instances [monitor-ec2-instances] To analyze EC2 instance metrics, you can select view filters based on the following predefined metrics, or you can add [custom metrics](/solutions/observability/infra-and-hosts/view-infrastructure-metrics-by-resource-type.md#custom-metrics). +:::{note} +:applies_to: stack: ga 9.3 +For EC2 instances, The [Infrastructure UI](/solutions/observability/infra-and-hosts/analyze-infrastructure-host-metrics.md) and [inventory rules](/solutions/observability/incident-management/create-an-inventory-rule.md) only support metric collected by the [EC2 integration](integration-docs://reference/aws/ec2.md). +::: + +### Entity definition [monitor-ec2-entity] +```{applies_to} +stack: ga 9.3 +``` + +| | | | +| --- | --- | --- | +| **Filter** | `event.module : aws` | Used to filter relevant data. | +| **Identifier** | `cloud.instance.id` | Used to identify each entity. | +| **Display value** | `cloud.instance.name` | Used as a display friendly value. | + +### Metrics [monitor-ec2-metrics] + | | | | --- | --- | | **CPU Usage** | Average of `aws.ec2.cpu.total.pct`. | @@ -33,6 +52,24 @@ To analyze EC2 instance metrics, you can select view filters based on the follow To analyze S3 bucket metrics, you can select view filters based on the following predefined metrics, or you can add [custom metrics](/solutions/observability/infra-and-hosts/view-infrastructure-metrics-by-resource-type.md#custom-metrics). +:::{note} +:applies_to: stack: ga 9.3 +For S3 buckets, the [Infrastructure UI](/solutions/observability/infra-and-hosts/analyze-infrastructure-host-metrics.md) and [inventory rules](/solutions/observability/incident-management/create-an-inventory-rule.md) only support metric data collected by the [S3 integration](integration-docs://reference/aws/s3.md). +::: + +### Entity definition [monitor-s3-entity] +```{applies_to} +stack: ga 9.3 +``` + +| | | +| --- | --- | +| **Filter** | `event.module : aws` | Used to filter relevant data. | +| **Identifier** | `aws.s3.bucket.name` | Used to identify each entity. | +| **Display value** | `aws.s3.bucket.name` | Used as a display friendly value. | + +### Metrics [monitor-s3-metrics] + | | | | --- | --- | | **Bucket Size** | Average of `aws.s3_daily_storage.bucket.size.bytes`. | @@ -46,6 +83,24 @@ To analyze S3 bucket metrics, you can select view filters based on the following To analyze SQS queue metrics, you can select view filters based on the following predefined metrics, or you can add [custom metrics](/solutions/observability/infra-and-hosts/view-infrastructure-metrics-by-resource-type.md#custom-metrics). +:::{note} +:applies_to: stack: ga 9.3 +For SQS queues, the [Infrastructure UI](/solutions/observability/infra-and-hosts/analyze-infrastructure-host-metrics.md) and [inventory rules](/solutions/observability/incident-management/create-an-inventory-rule.md) only support metric data collected by the [SQS integration](integration-docs://reference/aws/sqs.md). +::: + +### Entity definition [monitor-sqs-entity] +```{applies_to} +stack: ga 9.3 +``` + +| | | +| --- | --- | +| **Filter** | `event.module : aws` | Used to filter relevant data. | +| **Identifier** | `aws.sqs.queue.name` | Used to identify each entity. | +| **Display value** | `aws.sqs.queue.name` | Used as a display friendly value. | + +### Metrics [monitor-sqs-metrics] + | | | | --- | --- | | **Messages Available** | Max of `aws.sqs.messages.visible`. | @@ -59,6 +114,24 @@ To analyze SQS queue metrics, you can select view filters based on the following To analyze RDS database metrics, you can select view filters based on the following predefined metrics, or you can add [custom metrics](/solutions/observability/infra-and-hosts/view-infrastructure-metrics-by-resource-type.md#custom-metrics). +:::{note} +:applies_to: stack: ga 9.3 +For RDS databases, the [Infrastructure UI](/solutions/observability/infra-and-hosts/analyze-infrastructure-host-metrics.md) and [inventory rules](/solutions/observability/incident-management/create-an-inventory-rule.md) only support metric data collected by the [RDS](integration-docs://reference/aws/rds.md) integration. +::: + +### Entity definition [monitor-rds-entity] +```{applies_to} +stack: ga 9.3 +``` + +| | | +| --- | --- | +| **Filter** | `event.module : aws` | Used to filter relevant data. | +| **Identifier** | `aws.rds.db_instance.arn` | Used to identify each entity. | +| **Display value** | `aws.rds.db_instance.identifier` | Used as a display friendly value. | + +### Metrics [monitor-rds-metrics] + | | | | --- | --- | | **CPU Usage** | Average of `aws.rds.cpu.total.pct`. | @@ -67,4 +140,4 @@ To analyze RDS database metrics, you can select view filters based on the follow | **Active Transactions** | Average of `aws.rds.transactions.active`. | | **Latency** | Average of `aws.rds.latency.dml`. | -For information about the fields used by the Infrastructure UI to display AWS services metrics, see the [Infrastructure app fields](/reference/observability/fields-and-object-schemas.md). +For information about the fields used by the Infrastructure UI to display AWS services metrics, refer to the [Infrastructure app fields](/reference/observability/fields-and-object-schemas.md). \ No newline at end of file diff --git a/reference/observability/observability-container-metrics.md b/reference/observability/observability-container-metrics.md index cf4276d046..8e4dc586cd 100644 --- a/reference/observability/observability-container-metrics.md +++ b/reference/observability/observability-container-metrics.md @@ -2,6 +2,9 @@ mapped_pages: - https://www.elastic.co/guide/en/serverless/current/observability-container-metrics.html - https://www.elastic.co/guide/en/observability/current/container-metrics.html +applies_to: + stack: ga + serverless: ga products: - id: cloud-serverless - id: observability @@ -14,11 +17,25 @@ Learn about key container metrics displayed in the Infrastructure UI: * [Docker](#key-metrics-docker) * [Kubernetes](#key-metrics-kubernetes) - ## Docker container metrics [key-metrics-docker] These are the key metrics displayed for Docker containers. +:::{note} +:applies_to: stack: ga 9.3 +For Docker container metrics, the [Infrastructure UI](/solutions/observability/infra-and-hosts/analyze-infrastructure-host-metrics.md) and [inventory rules](/solutions/observability/incident-management/create-an-inventory-rule.md) only support metric data collected by the [Docker integration](integration-docs://reference/docker.md). +::: + +### Entity definition [monitor-docker-container-entity] +```{applies_to} +stack: ga 9.3 +``` + +| | | | +| --- | --- | --- | +| **Filter** | `event.module : "docker"` | Used to filter relevant data. | +| **Identifier** | `container.id` | Used to identify each entity. | +| **Display value** | `container.name` | Used as a display friendly value. | ### CPU usage metrics [key-metrics-docker-cpu] @@ -50,10 +67,25 @@ These are the key metrics displayed for Docker containers. | **Disk Write IOPS** | Average count of write operations from the device per second.

**Field Calculation:** `counter_rate(max(docker.diskio.write.ops), kql='docker.diskio.write.ops: *')`
| -## Kubernetes container metrics [key-metrics-kubernetes] +## {{k8s}} container metrics [key-metrics-kubernetes] + +These are the key metrics displayed for {{k8s}} (containerd) containers. + +:::{note} +:applies_to: stack: ga 9.3 +For {{k8s}} container metrics, the [Infrastructure UI](/solutions/observability/infra-and-hosts/analyze-infrastructure-host-metrics.md) and [inventory rules](/solutions/observability/incident-management/create-an-inventory-rule.md) only support metric data collected by the [{{k8s}} integration](integration-docs://reference/kubernetes.md). +::: -These are the key metrics displayed for Kubernetes (containerd) containers. +### Entity definition [monitor-k8s-container-entity] +```{applies_to} +stack: ga 9.3 +``` +| | | | +| --- | --- | --- | +| **Filter** | `event.module : "kubernetes"` | Used to filter relevant data. | +| **Identifier** | `container.id` | Used to identify each entity. | +| **Display value** | `container.name` | Used as a display friendly value. | ### CPU usage metrics [key-metrics-kubernetes-cpu] @@ -66,4 +98,4 @@ These are the key metrics displayed for Kubernetes (containerd) containers. | Metric | Description | | --- | --- | -| **Memory Usage (%)** | Average memory usage for the container.

**Field Calculation:** `average(kubernetes.container.memory.usage.limit.pct)`
| +| **Memory Usage (%)** | Average memory usage for the container.

**Field Calculation:** `average(kubernetes.container.memory.usage.limit.pct)`
| \ No newline at end of file diff --git a/reference/observability/observability-host-metrics.md b/reference/observability/observability-host-metrics.md index d6e7abc436..4113d1514d 100644 --- a/reference/observability/observability-host-metrics.md +++ b/reference/observability/observability-host-metrics.md @@ -2,6 +2,9 @@ mapped_pages: - https://www.elastic.co/guide/en/serverless/current/observability-host-metrics.html - https://www.elastic.co/guide/en/observability/current/host-metrics.html +applies_to: + stack: ga + serverless: ga products: - id: cloud-serverless - id: observability @@ -27,7 +30,18 @@ Refer to the following sections for host metrics and field calculation formulas * [Disk](#key-metrics-network) * [Legacy](#legacy-metrics) -### Hosts metrics [key-metrics-hosts] +### Entity definition [monitor-rds-entity] +```{applies_to} +stack: ga 9.3 +``` + +| | | +| --- | --- | +| **Filter** | `event.module: 'system'` or `metricset.module: 'system'` | Used to filter relevant data. | +| **Identifier** | `host.name` | Used to identify each entity. | +| **Display value** | `host.name` | Used as a display friendly value. | + +### Hosts count [key-metrics-hosts] | Metric | Description | | --- | --- | @@ -114,13 +128,24 @@ Refer to the following sections for host metrics and field calculation formulas * [Network](#otel-metrics-network) * [Disk](#otel-metrics-network) -### OpenTelemetry hosts metrics [otel-metrics-hosts] +### Entity definition [opentelemetry-host-entity] +```{applies_to} +stack: ga 9.3 +``` + +| | | +| --- | --- | +| **Filter** | `data_stream.dataset: 'hostmetricsreceiver.otel'` | Used to filter relevant data. | +| **Identifier** | `host.name` | Used to identify each entity. | +| **Display value** | `host.name` | Used as a display friendly value. | + +### Hosts count [otel-metrics-hosts] | Metric | Description | | --- | --- | | **Hosts** | Number of hosts returned by your search criteria.

**Field Calculation**: `unique_count(host.name)`
| -### OpenTelemetry CPU usage metrics [otel-metrics-cpu] +### CPU usage metrics [otel-metrics-cpu] | Metric | Description | | --- | --- | @@ -137,7 +162,7 @@ Refer to the following sections for host metrics and field calculation formulas | **Load (15m)** | 15 minute load average.

Load average gives an indication of the number of threads that are runnable (either busy running on CPU, waiting to run, or waiting for a blocking IO operation to complete).

**Field Calculation**: `average(metrics.system.cpu.load_average.15m)`
| | **Normalized Load** | 1 minute load average normalized by the number of CPU cores.

Load average gives an indication of the number of threads that are runnable (either busy running on CPU, waiting to run, or waiting for a blocking IO operation to complete).

100% means the 1 minute load average is equal to the number of CPU cores of the host.

Taking the example of a 32 CPU cores host, if the 1 minute load average is 32, the value reported here is 100%. If the 1 minute load average is 48, the value reported here is 150%.

**Field Calculation**: `average(metrics.system.cpu.load_average.1m) / max(metrics.system.cpu.logical.count)`
| -### OpenTelemetry memory metrics [otel-metrics-memory] +### Memory metrics [otel-metrics-memory] | Metric | Description | | --- | --- | @@ -148,20 +173,20 @@ Refer to the following sections for host metrics and field calculation formulas | **Memory Usage (%)** | Percentage of main memory usage excluding page cache.

This includes resident memory for all processes plus memory used by the kernel structures and code apart from the page cache.

A high level indicates a situation of memory saturation for the host. For example, 100% means the main memory is entirely filled with memory that can’t be reclaimed, except by swapping out.

**Field Calculation**: `average(system.memory.utilization, kql='state: used') + average(system.memory.utilization, kql='state: buffered') + average(system.memory.utilization, kql='state: slab_reclaimable') + average(system.memory.utilization, kql='state: slab_unreclaimable')`
| | **Memory Used** | Main memory usage excluding page cache.

**Field Calculation**: `average(metrics.system.memory.usage, kql='state: used') + average(metrics.system.memory.usage, kql='state: buffered') + average(metrics.system.memory.usage, kql='state: slab_reclaimable') + average(metrics.system.memory.usage, kql='state: slab_unreclaimable')`
| -### OpenTelemetry log metrics [otel-metrics-log] +### Log metrics [otel-metrics-log] | Metric | Description | | --- | --- | | **Log Rate** | Derivative of the cumulative sum of the document count scaled to a 1 second rate. This metric relies on the same indices as the logs.

**Field Calculation**: `cumulative_sum(doc_count)`
| -### OpenTelemetry network metrics [otel-metrics-network] +### Network metrics [otel-metrics-network] | Metric | Description | | --- | --- | | **Network Inbound (RX)** | Number of bytes that have been received per second on the public interfaces of the hosts.

**Field Calculation**: `8 * counter_rate(max(metrics.system.network.io, kql='direction: receive')))`
| | **Network Outbound (TX)** | Number of bytes that have been sent per second on the public interfaces of the hosts.

**Field Calculation**: `8 * counter_rate(max(metrics.system.network.io, kql='direction: transmit'))`
| -### OpenTelemetry disk metrics [otel-metrics-disk] +### Disk metrics [otel-metrics-disk] | Metric | Description | | --- | --- | @@ -171,6 +196,4 @@ Refer to the following sections for host metrics and field calculation formulas | **Disk Usage - Available (%)** | Percentage of disk space available.

**Field Calculation**: `average(system.filesystem.usage, kql='state: free')`
| | **Disk Usage - Used (%)** | Percentage of disk space used.

**Field Calculation**: `1 - sum(metrics.system.filesystem.usage, kql='state: free') / sum(metrics.system.filesystem.usage)`
| | **Disk Write IOPS** | Average count of write operations from the device per second.

**Field Calculation**: `counter_rate(max(system.disk.operations, kql='attributes.direction: write'))`
| -| **Disk Write Throughput** | Average number of bytes written from the device per second.

**Field Calculation**: `counter_rate(max(system.disk.io, kql='attributes.direction: write'))')`
| - - +| **Disk Write Throughput** | Average number of bytes written from the device per second.

**Field Calculation**: `counter_rate(max(system.disk.io, kql='attributes.direction: write'))')`
| \ No newline at end of file diff --git a/reference/observability/observability-kubernetes-pod-metrics.md b/reference/observability/observability-kubernetes-pod-metrics.md index 4af92c6331..aee350cc96 100644 --- a/reference/observability/observability-kubernetes-pod-metrics.md +++ b/reference/observability/observability-kubernetes-pod-metrics.md @@ -2,14 +2,35 @@ mapped_pages: - https://www.elastic.co/guide/en/serverless/current/observability-kubernetes-pod-metrics.html - https://www.elastic.co/guide/en/observability/current/kubernetes-pod-metrics.html +applies_to: + stack: ga + serverless: ga products: - id: cloud-serverless - id: observability --- -# Kubernetes pod metrics [observability-kubernetes-pod-metrics] +# {{k8s}} pod metrics [observability-kubernetes-pod-metrics] -To analyze Kubernetes pod metrics, you can select view filters based on the following predefined metrics, or you can add [custom metrics](/solutions/observability/infra-and-hosts/view-infrastructure-metrics-by-resource-type.md#custom-metrics). +To analyze {{k8s}} pod metrics, you can select view filters based on the following predefined metrics, or you can add [custom metrics](/solutions/observability/infra-and-hosts/view-infrastructure-metrics-by-resource-type.md#custom-metrics). + +:::{note} +:applies_to: stack: ga 9.3 +For {{k8s}} pod metrics, the [Infrastructure UI](/solutions/observability/infra-and-hosts/analyze-infrastructure-host-metrics.md) and [inventory rules](/solutions/observability/incident-management/create-an-inventory-rule.md) only support metric data collected by the [{{k8s}} integration](integration-docs://reference/kubernetes.md). +::: + +## Entity definition [monitor-k8s-pods-entity] +```{applies_to} +stack: ga 9.3 +``` + +| | | | +| --- | --- | --- | +| **Filter** | `event.module: "kubernetes"` | Used to filter relevant data. | +| **Identifier** | `kubernetes.pod.uid` | Used to identify each entity. | +| **Display value** | `kubernetes.pod.name` | Used as a display friendly value. | + +## Metrics [monitor-k8s-pods-metrics] | | | | --- | --- | @@ -18,4 +39,4 @@ To analyze Kubernetes pod metrics, you can select view filters based on the foll | **Inbound Traffic** | Derivative of the maximum of `kubernetes.pod.network.rx.bytes` scaled to a 1 second rate. | | **Outbound Traffic** | Derivative of the maximum of `kubernetes.pod.network.tx.bytes` scaled to a 1 second rate. | -For information about the fields used by the Infrastructure UI to display Kubernetes pod metrics, see the [Infrastructure app fields](/reference/observability/fields-and-object-schemas.md). +For information about the fields used by the Infrastructure UI to display {{k8s}} pod metrics, see the [Infrastructure app fields](/reference/observability/fields-and-object-schemas.md). \ No newline at end of file diff --git a/solutions/observability/incident-management/create-an-inventory-rule.md b/solutions/observability/incident-management/create-an-inventory-rule.md index 7a5ad53ffa..4a767d1704 100644 --- a/solutions/observability/incident-management/create-an-inventory-rule.md +++ b/solutions/observability/incident-management/create-an-inventory-rule.md @@ -36,8 +36,8 @@ When you select **Create inventory alert**, the parameters you configured on the Conditions for each rule can be applied to specific metrics relating to the inventory type you select. You can choose the aggregation type, the metric, and by including a warning threshold value, you can be alerted on multiple threshold values based on severity scores. When creating the rule, you can still get notified if no data is returned for the specific metric or if the rule fails to query {{es}}. :::{note} -{applies_to}`{stack: "ga 9.2", serverless: "ga"}` -Most inventory types respect the default data collection method (for example, [Elastic system integration](integration-docs://reference/system/index.md)). For the `Hosts` inventory type, however, you can use the **Schema** dropdown menu to explicitly target host data collected using **OpenTelemetry** or the **Elastic System Integration**. +:applies_to: {"stack": "ga 9.2", "serverless": "ga"}` +Most inventory types respect the default data collection method (for example, [Elastic System Integration](integration-docs://reference/system/index.md)). For the `Hosts` inventory type, however, you can use the **Schema** dropdown menu to explicitly target host data collected using **OpenTelemetry** or the **Elastic System Integration**. ::: In the following example, Kubernetes Pods is the selected inventory type. The conditions state that you will receive a critical alert for any pods within the `ingress-nginx` namespace with a memory usage of 95% or above and a warning alert if memory usage is 90% or above. The chart shows the results of applying the rule to the last 20 minutes of data. Note that the chart time range is 20 times the value of the look-back window specified in the `FOR THE LAST` field. @@ -47,6 +47,15 @@ In the following example, Kubernetes Pods is the selected inventory type. The co :screenshot: ::: +### Supported data by inventory type + +For more on the data supported by each inventory type, refer to the following references: + +* [Hosts](../../../reference/observability/observability-host-metrics.md) +* [{{k8s}} Pods](../../../reference/observability/observability-kubernetes-pod-metrics.md) +* [Docker Containers](../../../reference/observability/observability-container-metrics.md) +* [AWS](../../../reference/observability/observability-aws-metrics.md) + ## Add actions [action-types-infrastructure] You can extend your rules with actions that interact with third-party systems, write to logs or indices, or send user notifications. You can add an action to a rule at any time. You can create rules without adding actions, and you can also define multiple actions for a single rule. diff --git a/solutions/observability/infra-and-hosts/analyze-compare-hosts.md b/solutions/observability/infra-and-hosts/analyze-compare-hosts.md index 1658716995..1b6c0a0484 100644 --- a/solutions/observability/infra-and-hosts/analyze-compare-hosts.md +++ b/solutions/observability/infra-and-hosts/analyze-compare-hosts.md @@ -163,6 +163,7 @@ serverless: ga The **Schema** menu shows the available data collection schemas for the current query. If host data from both the Elastic System integration and OpenTelemetry is available, the schema defaults to **OpenTelemetry**. Select **Elastic System Integration** to see host data collected by the Elastic System integration. +Refer to [Host metrics](../../../reference/observability/observability-host-metrics.md) for more on supported data types for OpenTelemetry and the Elastic System integration. ## View host details [view-host-details] diff --git a/solutions/observability/infra-and-hosts/view-infrastructure-metrics-by-resource-type.md b/solutions/observability/infra-and-hosts/view-infrastructure-metrics-by-resource-type.md index bfce569ea2..8342989ac4 100644 --- a/solutions/observability/infra-and-hosts/view-infrastructure-metrics-by-resource-type.md +++ b/solutions/observability/infra-and-hosts/view-infrastructure-metrics-by-resource-type.md @@ -39,10 +39,10 @@ Need help getting started? Follow the steps in [Get started with system metrics] To get started with your analysis, select the type of resources you want to show in the high-level view. From the **Show** menu, select one of the following: -* **Hosts** — the default -* **Kubernetes Pods** -* **Docker Containers** — shows *all* containers, not just Docker -* **AWS** — includes EC2 instances, S3 buckets, RDS databases, and SQS queues +* **Hosts**: the default view. Refer to [Host metrics](../../../reference/observability/observability-host-metrics.md) for more on supported data types for this view. +* **Kubernetes Pods**: Refer to [{{k8s}} pod metrics](../../../reference/observability/observability-kubernetes-pod-metrics.md) for more on supported data types for this view. +* **Docker Containers**: shows *all* containers, not only Docker containers. Refer to [Container metrics](../../../reference/observability/observability-container-metrics.md) for more on supported data types for this view. +* **AWS**: includes EC2 instances, S3 buckets, RDS databases, and SQS queues. Refer to [AWS metrics](../../../reference/observability/observability-aws-metrics.md) for more on supported data types for this view. When you hover over each resource in the waffle map, the metrics specific to that resource are displayed. @@ -59,6 +59,10 @@ To examine the metrics for a specific time, use the time filter to select the da ## View host metrics [analyze-hosts-inventory] +:::{note} +Refer to [Host metrics](../../../reference/observability/observability-host-metrics.md) for more on supported data types for this view. +::: + By default the **Infrastructure Inventory** page displays a waffle map that shows the hosts you are monitoring and the current CPU usage for each host. Alternatively, you can click the **Table view** icon ![table view icon](/solutions/images/observability-table-view-icon.png "") to switch to a table view. Without leaving the **Infrastructure Inventory** page, you can view enhanced metrics relating to each host running in your infrastructure. On the waffle map, select a host to display the host details overlay. @@ -262,6 +266,10 @@ These metrics are also available when viewing hosts on the **Hosts** page. ## View container metrics [analyze-containers-inventory] +:::{note} +Refer to [Container metrics](../../../reference/observability/observability-container-metrics.md) for more on supported data types for this view. +::: + When you select **Docker containers**, the **Infrastructure inventory** page displays a waffle map that shows the containers you are monitoring and the current CPU usage for each container. Alternatively, you can click the **Table view** icon ![Table view icon](/solutions/images/serverless-table-view-icon.png "") to switch to a table view. Without leaving the **Infrastructure inventory** page, you can view enhanced metrics relating to each container running in your infrastructure. @@ -352,6 +360,10 @@ To view the logs in the {{logs-app}} for a detailed analysis, click **Open in Lo ## View metrics for other resources [analyze-resource-metrics] +:::{note} +Refer to [{{k8s}} pod metrics](../../../reference/observability/observability-kubernetes-pod-metrics.md) and [AWS metrics](../../../reference/observability/observability-aws-metrics.md) for more on supported data types for this view. +::: + When you have searched and filtered for a specific resource, you can drill down to analyze the metrics relating to it. For example, when viewing Kubernetes Pods in the high-level view, click the Pod you want to analyze and select **Kubernetes Pod metrics** to see detailed metrics: :::{image} /solutions/images/observability-pod-metrics.png