Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Commit 081ec55

Browse files
committed
add-mitchell-feedback
1 parent 1a7de55 commit 081ec55

File tree

5 files changed

+8
-291
lines changed

5 files changed

+8
-291
lines changed

infrastructure/monitor/k8s-nav.rst

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,6 @@ Monitor Kubernetes
77
.. meta::
88
:description: Learn how to monitor Kubernetes resources with Splunk Observability Cloud.
99

10-
.. note:: The following topic describes the new Kubernetes navigator. See :ref:`infrastructure-k8s` for documentation on the classic Kubernetes navigator.
11-
1210
You can monitor Kubernetes metrics with Splunk Observability Cloud. Splunk Observability Cloud uses the Splunk Distribution of OpenTelemetry Collector for Kubernetes to provide robust infrastructure monitoring capabilities. To learn more, see :ref:`otel-intro`.
1311

1412
Prerequisites
@@ -113,9 +111,9 @@ Troubleshoot performance with the analyzer
113111

114112
.. note:: The analyzer is only available on the Kubernetes nodes, pods, and containers navigators.
115113

116-
The Kubernetes analyzer, accessed through the :guilabel:`K8s analyzer` tab, helps you troubleshoot Kubernetes problems at scale by highlighting Kubernetes instances that are in a bad state, such as nodes that are not ready. The analyzer produces theories about what those instances might have in common, such as that all of the instances are running the same workload or all instances are located in the same AWS region. Select a finding in the analyzer tab to filter the map.
114+
You can access the Kubernetes analyzer through the :guilabel:`K8s analyzer` tab. The analyzer helps you troubleshoot Kubernetes problems at scale by highlighting Kubernetes instances that are in a bad state, such as nodes that are not ready. The analyzer produces theories about what those instances might have in common, such as that all of the instances are running the same workload or all instances are located in the same AWS region. Select a finding in the analyzer to filter the map.
117115

118-
The analyzer tab displays suggested filters for the elements selected in the table or heat map view. Select links in the analyzer tab to add filters to the table or heat map view and explore conditions across your entire Kubernetes environment.
116+
The analyzer displays suggested filters for the elements selected in the table or heat map view. Select links in the analyzer to add filters to the table or heat map view and explore conditions across your entire Kubernetes environment.
119117

120118
The analyzer uses AI-driven insights to examine potential patterns between nodes, pods, or containers. The trouble indicators are:
121119

0 commit comments

Comments
 (0)