# About Kubernetes Monitoring ![rw-book-cover](https://grafana.com/meta-generator/About%20Kubernetes%20Monitoring.jpg) URL:: https://grafana.com/docs/grafana-cloud/kubernetes-monitoring/about-k8s-monitoring/ Author:: Grafana Labs ## Highlights > Specifically, Kubernetes Monitoring give you access to the following: > Component > Description > Manifests > Preconfigured manifests for deploying Grafana Agent, Grafana’s telemetry collector, and kube-state-metrics to your clusters. See [kube-state-metrics](https://grafana.com/docs/grafana-cloud/kubernetes-monitoring/about-k8s-monitoring#kube-state-metrics) to learn which kube-state-metrics are scraped by default with Kubernetes Monitoring. > Dashboards > Nine Grafana [dashboards](https://grafana.com/docs/grafana-cloud/kubernetes-monitoring/navigate-k8s-monitoring#dashboards) to drill into resource usage and cluster operations, from the multi-cluster level down to individual containers and Pods. > Recording rules > A set of [recording rules](https://grafana.com/docs/grafana-cloud/kubernetes-monitoring/about-k8s-monitoring#recording-rules) to speed up dashboard queries. > Alerting rules > A set of [alerting rules](https://grafana.com/docs/grafana-cloud/kubernetes-monitoring/about-k8s-monitoring#alerting-rules) to alert on conditions. For example: Pods crash looping and Pods getting stuck in “not ready” status. > Allowlist > An optional preconfigured [allowlist of metrics](https://grafana.com/docs/grafana-cloud/kubernetes-monitoring/about-k8s-monitoring#allowlists-for-managing-metrics) referenced in the above dashboards, recording rules, and alerting rules to reduce your active series usage while still giving you visibility into core cluster metrics. > Events > Grafana Agent can configure an eventhandler integration to watch for [Kubernetes Events](https://grafana.com/docs/grafana-cloud/kubernetes-monitoring/configuration/events/) in your clusters. ([View Highlight](https://read.readwise.io/read/01gyw8mw81dcvqxv6fzgbxjrx1)) > The default Kubernetes Monitoring setup instructions roll out a Grafana Agent DaemonSet to collect logs from all pods running in your cluster and ship these to Grafana Cloud Loki. ([View Highlight](https://read.readwise.io/read/01gyw8vtwh7an7yt01kq3jyj4k)) > Kubernetes Monitoring does not yet support out-of-the-box configuration for shipping traces to your hosted Tempo endpoint. ([View Highlight](https://read.readwise.io/read/01gyw8w9xexf7q0f4gjsa2s99y)) > I’m already sending kube-state-metrics to Prometheus - do I still need to use Grafana Agent?[](https://grafana.com/docs/grafana-cloud/kubernetes-monitoring/about-k8s-monitoring#im-already-sending-kube-state-metrics-to-prometheus---do-i-still-need-to-use-grafana-agent) > You do not need to use Grafana Agent if you are already sending kube-state-metrics. Kubernetes Monitoring shows data in the [**Cluster navigation**](https://grafana.com/docs/grafana-cloud/kubernetes-monitoring/navigate-k8s-monitoring#cluster-navigation) tab as long as you are using kube-state metrics version 2.1 or greater. However, some features (like pod logs, Kubernetes events, and resource management) rely on specific recording rules and metrics that ship with Grafana Agent, and may not show properly. To switch to Grafana agent, make sure to first remove the existing job that is sending metrics. ([View Highlight](https://read.readwise.io/read/01gyw8xqgrgs01c1x1qyzm29j0)) > If you are already sending kube-state-metrics to Grafana Cloud with Grafana Agent through the Kubernetes integration, no action is needed—Kubernetes Monitoring uses the existing metrics and you can start using the Kubernetes Monitoring preconfigured dashboards and alerting immediately. ([View Highlight](https://read.readwise.io/read/01gyw8xx80ycmtq5tyfskcv6d2)) --- Title: About Kubernetes Monitoring Author: Grafana Labs Tags: readwise, articles date: 2024-01-30 --- # About Kubernetes Monitoring ![rw-book-cover](https://grafana.com/meta-generator/About%20Kubernetes%20Monitoring.jpg) URL:: https://grafana.com/docs/grafana-cloud/kubernetes-monitoring/about-k8s-monitoring/ Author:: Grafana Labs ## AI-Generated Summary About Kubernetes Monitoring Grafana Kubernetes Monitoring lets you view all of your Kubernetes data in one place. By shipping kube-state-metrics to Grafana Cloud, you can inspect the health of your clusters, containers, and pods with little or no required configuration. You can also access preconfigured dashboards, alert rules, and recording rules. Get started Select a question to learn more about Kubernetes Monitoring. How do I use Kubernetes Monitoring? What’s the easiest way to get started? ## Highlights > Specifically, Kubernetes Monitoring give you access to the following: > Component > Description > Manifests > Preconfigured manifests for deploying Grafana Agent, Grafana’s telemetry collector, and kube-state-metrics to your clusters. See [kube-state-metrics](https://grafana.com/docs/grafana-cloud/kubernetes-monitoring/about-k8s-monitoring#kube-state-metrics) to learn which kube-state-metrics are scraped by default with Kubernetes Monitoring. > Dashboards > Nine Grafana [dashboards](https://grafana.com/docs/grafana-cloud/kubernetes-monitoring/navigate-k8s-monitoring#dashboards) to drill into resource usage and cluster operations, from the multi-cluster level down to individual containers and Pods. > Recording rules > A set of [recording rules](https://grafana.com/docs/grafana-cloud/kubernetes-monitoring/about-k8s-monitoring#recording-rules) to speed up dashboard queries. > Alerting rules > A set of [alerting rules](https://grafana.com/docs/grafana-cloud/kubernetes-monitoring/about-k8s-monitoring#alerting-rules) to alert on conditions. For example: Pods crash looping and Pods getting stuck in “not ready” status. > Allowlist > An optional preconfigured [allowlist of metrics](https://grafana.com/docs/grafana-cloud/kubernetes-monitoring/about-k8s-monitoring#allowlists-for-managing-metrics) referenced in the above dashboards, recording rules, and alerting rules to reduce your active series usage while still giving you visibility into core cluster metrics. > Events > Grafana Agent can configure an eventhandler integration to watch for [Kubernetes Events](https://grafana.com/docs/grafana-cloud/kubernetes-monitoring/configuration/events/) in your clusters. ([View Highlight](https://read.readwise.io/read/01gyw8mw81dcvqxv6fzgbxjrx1)) > The default Kubernetes Monitoring setup instructions roll out a Grafana Agent DaemonSet to collect logs from all pods running in your cluster and ship these to Grafana Cloud Loki. ([View Highlight](https://read.readwise.io/read/01gyw8vtwh7an7yt01kq3jyj4k)) > Kubernetes Monitoring does not yet support out-of-the-box configuration for shipping traces to your hosted Tempo endpoint. ([View Highlight](https://read.readwise.io/read/01gyw8w9xexf7q0f4gjsa2s99y)) > I’m already sending kube-state-metrics to Prometheus - do I still need to use Grafana Agent?[](https://grafana.com/docs/grafana-cloud/kubernetes-monitoring/about-k8s-monitoring#im-already-sending-kube-state-metrics-to-prometheus---do-i-still-need-to-use-grafana-agent) > You do not need to use Grafana Agent if you are already sending kube-state-metrics. Kubernetes Monitoring shows data in the [**Cluster navigation**](https://grafana.com/docs/grafana-cloud/kubernetes-monitoring/navigate-k8s-monitoring#cluster-navigation) tab as long as you are using kube-state metrics version 2.1 or greater. However, some features (like pod logs, Kubernetes events, and resource management) rely on specific recording rules and metrics that ship with Grafana Agent, and may not show properly. To switch to Grafana agent, make sure to first remove the existing job that is sending metrics. ([View Highlight](https://read.readwise.io/read/01gyw8xqgrgs01c1x1qyzm29j0)) > If you are already sending kube-state-metrics to Grafana Cloud with Grafana Agent through the Kubernetes integration, no action is needed—Kubernetes Monitoring uses the existing metrics and you can start using the Kubernetes Monitoring preconfigured dashboards and alerting immediately. ([View Highlight](https://read.readwise.io/read/01gyw8xx80ycmtq5tyfskcv6d2))