# K8s Monitoring

K8s Monitoring is a Helm chart that installs a complete observability stack to capture metrics, logs, and traces from your Kubernetes cluster, giving homelabbers and cluster operators centralized telemetry for Grafana. It is open source and self-hosted, installable on Kubernetes (Helm).

Canonical page: https://ourlocalhost.com/app/4696/k8s-monitoring

## Description

K8s Monitoring is a Helm chart that installs a complete observability stack to capture metrics, logs, and traces from your Kubernetes cluster, giving homelabbers and cluster operators centralized telemetry for Grafana.

## Platform availability

Available on 1 of 10 platforms: Helm.

## Health score

70/100 (Good), based on 3 of 4 factors.
- Maintained: 100 (last commit 15 days ago)
- Popular: 57 (696 GitHub stars)
- Easy to install: 25 (1 install platform, install notes)

## Links

- GitHub: https://github.com/grafana/k8s-monitoring-helm
- Kubernetes (Helm): https://artifacthub.io/packages/helm/grafana/k8s-monitoring

## Common questions

### Which Kubernetes metrics should I capture with a self-hosted monitoring setup?

A Grafana Labs guide suggests following a five-part approach that focuses on key Kubernetes metrics and best practices.

### Should multiple Kubernetes clusters use one central monitoring stack or separate stacks?

A Kubernetes forum thread notes that aggregating all monitoring data in a single Prometheus can be complex, so teams weigh centralized monitoring against per-cluster stacks.

### Should monitoring run on a separate server when the main host already runs many containers?

A self-hosting user with over 130 Docker containers says things are getting messy and ideally wants monitoring on a completely separate server, while asking whether that is correct.

---
Source: Our Local Host (https://ourlocalhost.com/app/4696/k8s-monitoring), the self-hosted and open-source app directory.
