Docs » Splunk Infrastructure Monitoring でサービスとホストを監視する » Kubernetesを監視する

Kubernetesを監視する 🔗

注釈

以下のトピックでは、新しいKubernetesナビゲーターについて説明します。従来のKubernetesナビゲーターに関するドキュメントは Kubernetesを監視する(クラシック版) を参照してください。

Splunk Observability Cloud で Kubernetes のメトリクスを監視できます。Splunk Observability Cloud は、Splunk Distribution of OpenTelemetry Collector for Kubernetes を使用して、堅牢なInfrastructure Monitoring 機能を提供します。詳細については、Splunk Distribution of the OpenTelemetry Collector の利用開始 を参照してください。

前提条件 🔗

To start monitoring Kubernetes resources, you must:

Kubernetesナビゲーター 🔗

注釈

The following sections describe components specific to the Kubernetes navigators. For information on components shared by all navigators, see Splunk Infrastructure Monitoring でナビゲーターを使用する.

On the Infrastructure landing page, you can view the summary cards for Kubernetes navigators under the Kubernetes section.

The following table describes the Kubernetes navigators:

Kubernetes navigator

説明

使用して実行する操作

  • ノード

  • ポッド

  • コンテナ

  • Get an overview of your Kubernetes infrastructure

  • Monitor the health of part of your Kubernetes infrastructure

  • Identify and diagnose an issue with part of your Kubernetes infrastructure

  • View services and hosts running on Kubernetes

  • ワークロード

  • Deployments

  • ReplicaSets

  • StatefulSets

  • DaemonSets

  • Jobs

  • CronJobs

  • Services

  • Resources

Provides a table and heat map view of Kubernetes objects across your infrastructure

  • Monitor Kubernetes instances across your infrastructure

  • Monitor a specific subset of instances, such as workloads running in a particular namespace

  • View services and hosts running on Kubernetes

Hierarchy map 🔗

注釈

The hierarchy map is only available on the Kubernetes nodes, pods, and containers navigators.

Monitor your Kubernetes infrastructure with an interactive hierarchical map that displays the child resources associated with a selected Kubernetes instance. You can select elements in the map to drill down into them, or use the filter to explore your data. The level of detail shown on the map is dynamic and depends on the number of elements shown.

To navigate to the hierarchy map:

  1. On the Infrastructure landing page, select the Kubernetes nodes, pods, or containers navigator.

  2. The table view displays by default. Select an instance from the table.

  3. Expand the hierarchy map.

    Hierarchy map view in the Kubernetes nodes navigator.

Nodes, pods, and containers are colored by health and status, as reported by Kubernetes:

  • ノードは条件によって色分けされています: Node ReadyMemory PressurePID PressureDisk PressureNetwork UnavailableOut of Disk

  • ポッドは相によって色分けされています: RunningPendingSucceededFailedUnknown

  • コンテナはステータスごとに色分けされています: ReadyNot ReadyUnknown

Investigate instances in the hierarchy map 🔗

  • Breadcrumb navigation: Switch to different instances and jump across entity levels using the breadcrumb navigation bar.

  • Hover: Get more information about an instance, including its status or phase, by hovering over that instance.

  • Select and zoom: Drill down into an instance and change the zoom level of the map, if applicable, by selecting the instance. Details about the instance display in the sidebar, in the About this <Entity_Type> panel.

  • Filter: Filter the map by any available metadata in your Kubernetes data, such as a namespace, a workload, or any other key-value pair. When you apply a filter, the map highlights instances that match the filter. You can still hover over the dimmed instances to view details about them.

Analyzer 🔗

注釈

The Analyzer is only available on the Kubernetes nodes, pods, and containers navigators.

The Analyzer, accessed through the 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 panel to filter the map.

The Analyzer panel displays suggested filters for the elements selected in the table or heat map view. Select links in the Analyzer panel to add filters to the table or heat map view and explore conditions across your entire Kubernetes environment.

The Analyzer uses AI-driven insights to examine patterns that nodes, pods, or containers could have in common. The trouble indicators are:

  • Pods that are in pending status

  • Pods that are in failed status

  • Pods with unknown condition

  • Containers with high restart counts

  • Nodes not ready

  • Nodes with unknown condition

  • Nodes experiencing high CPU

  • Nodes experiencing high memory

The Analyzer displays overrepresented metrics properties for known conditions, such as pods in pending status, pods in failed status, and so on. You can use properties that are highly correlated with these conditions to filter the table or heat map. You can explore data about each of those elements in the navigator using context-sensitive dashboards. This enables you to identify the underlying patterns noticeable on the filtered map that might be correlated with Kubernetes issues. For example, if all failed pods are in certain types of clusters, the Analyzer provides suggested paths to follow to troubleshoot such issues.

View services and hosts running on Kubernetes 🔗

Apart from monitoring your Kubernetes infrastructure, you can also track services and hosts running on Kubernetes in the navigator sidebar. When you select a service or host from the sidebar, you are switching to the navigator for that service or host instance.

次のステップ 🔗

また、以下の表で説明するように、Kubernetesクラスタに関連するデータをエクスポートして監視することもできます。

でデータを取得する

を監視する

説明

Kubernetesクラスタが稼働しているクラウドサービスプロバイダーに接続します (ある場合)。

バックエンドアプリケーションをインストルメンテーションして、スパンを Splunk APM に送信する

Splunk APMの概要

Kubernetesクラスタで実行されているアプリケーションからメトリクスとスパンを収集します。

This page was last updated on 2024年11月08日.