Integration · Containers
Kubernetes
DaemonSet, node and pod metrics, RBAC-minimal.
What gets collected
One DaemonSet per node plus one Deployment for control-plane scrapes. A ServiceMonitor CRD covers Prometheus-compatible endpoints in the cluster.
Requirements
- ✓Kubernetes 1.24+
- ✓RBAC: get/list/watch pods,nodes
- ✓Helm 3
- ✓DaemonSet per node
Key metrics
Collected out of the box. Every metric is available in dashboards, alerts and PromQL.
pod.cpupod.memnode.pressurecontainer.restartskube.deployment.replicaskube.pod.phaseSetup steps
- 1
helm repo add unimoni https://charts.unimoni.io - 2
helm install unimoni unimoni/agent - 3Optional: a ServiceMonitor for your own pod metrics
After install
- · Metrics show up on the dashboard within 15-30 seconds
- · Integration labels flow into filters automatically
- · Dashboard presets for common metrics are available in the editor
More in the docs
Kubernetes
Frequently asked questions
- What does Unimoni collect from Kubernetes?
- DaemonSet, node and pod metrics, RBAC-minimal. Every metric lands in the same TSDB as the rest of your stack, so you can build dashboards and alerts across Kubernetes and everything else in one place.
- How long does it take to connect Kubernetes?
- Usually a few minutes: a handful of steps, no code changes. Metrics show up on your dashboards within 15–30 seconds of the first scrape.
- What access does the Kubernetes integration need?
- Only the minimum listed under Requirements above — a scoped token or role, nothing more. Unimoni asks for the least privilege each system supports.
- Is Kubernetes monitoring available self-hosted and on the free plan?
- Yes. Every integration works identically on Unimoni Cloud and self-hosted, and is included from the free tier up.