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…
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
70/100 Good
- Maintained
- 100last commit 15 days ago
- Popular
- 57696 GitHub stars
- Easy to install
- 251 install platform, install notes
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today
- GitHub stars
- 696
- Open issues
- 190
- Last commit
- 2026-11-06
- Latest release
- k8s-monitoring-4.6.0
- License
- Apache-2.0
- Activity
- rising
Checked 14 days ago - source: GitHub (grafana/k8s-monitoring-helm)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Set up cluster login details Connect with a kubeconfig file or Kubernetes service account before first use. Without valid cluster access the monitor has nothing to show, and these credentials should be kept private because they can access your cluster. source
- Choose the right namespace Tell the monitor which namespace to search for resources. Kubernetes keeps resources separate by namespace, so a wrong or missing namespace makes resources look missing. source
- Use the exact resource type Use the exact API version and kind, such as apps/v1 and Deployment. If the type does not match, the request fails even when the resource exists. source
Fetched 40 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
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.
Answers sourced from discuss.kubernetes.io, www.reddit.com, www.redditmedia.com
Community
- A guide to Kubernetes Monitoring: In this 5 part series from ... - Reddit (reddit)
- Monitoring K8s : r/kubernetes - Reddit (reddit)
- Use central monitoring for multiple k8s cluster or each have their own (forum)
Collected 48 days ago - public community threads