kube-state-metrics
prometheus-operator
kube-state-metrics | prometheus-operator | |
---|---|---|
33 | 39 | |
5,102 | 8,751 | |
1.2% | 0.7% | |
9.1 | 9.7 | |
9 days ago | 8 days ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
kube-state-metrics
- Do we have any Prometheus metric to get the kubernetes cluster-level CPU/Memory requests/limits?
-
10 Kubernetes Visualization Tool that You Can't Afford to Miss
git clone https://github.com/kubernetes/kube-state-metrics.git
-
Why is the Prometheus metric 'kube_pod_completion_time' returning empty query results?
https://github.com/kubernetes/kube-state-metrics/blob/main/docs/pod-metrics.md According to this github repo completion is responsible of termination date if I correctly understood .
-
Google Kubernetes Engine's metrics vs Self-managed
kube-state-metrics
-
Prometheus node exporter and cadvisor to send metrics to central prometheus cluster
Those are entirely different types of data. You can get that from something like kube-state-metrics
-
Scaling kube-state-metrics in large cluster
I've never had a cluster of that size, so take it with a grain of salt - but maybe you could try purpose-based sharding? KSM has allowlist and denylist config flags, for configuring which metrics it exposes https://github.com/kubernetes/kube-state-metrics/blob/main/docs/cli-arguments.md
-
Questions about Kubernetes
Kubernetes itself will not notify you, the way I've seen people do this, is to use something like kube-state-metrics or node_exporter, export that to Prometheus (or preferrably VictoriaMetrics because Prometheus is terrible IMO), and then setup alarms on that with alertmanager or equivalent, or just look at dashboards regularly with Grafana. Realistically I recommend only setting alerts on disk usage and application/database latency. CPU and memory utilization isn't a great metric to alert on a lot of the time.
-
EKS scalability best practices
Another tip that you could consider spelling out a little more, is to monitor the number of resources created by Kind. This is somewhat mentioned for jobs and services, but any Kind of which thousands of resources are created will put stress on the control-plane. The total number of resources per namespace/cluster can be monitored with kube-state-metrics. KSM does not emit metrics of resources created from CRDs. These metrics can be implemented with KSM's custom resource state metrics: https://github.com/kubernetes/kube-state-metrics/blob/main/docs/customresourcestate-metrics.md
-
Observability-Landscape-as-Code in Practice
We then have various other Metrics called Kubernetes Workload Metrics. These are the dashboards with names that start with “Kubernetes / Compute Resources / Workload”. These dashboards are specific to the services you are running. They take into account the Kubernetes Workloads in your various namespaces, using kube-state-metrics. For a closer look, check out otel_demo_app_k8s_dashboard.tf.
-
Kubernetes Costs: Effective Cost Optimization Strategies To Reduce Your k8s Bill
The first step to optimizing costs is gaining visibility into your costs using tools. Kubernetes provides a Metrics Server and kube-state-metrics that can give you the overall picture of resource utilization by your cluster. There are more tools that provide more granular breakdowns and provide dashboards with business metrics, infra cost, and alerting functionalities. Here are some strategies to optimize your resource utilization and cloud bills on k8s.
prometheus-operator
-
Smart-Cash project -Adding monitoring to EKS using Prometheus operator
The project repository for Prometheus-operator can be found here, The repo defines the CRDs and the controller. You can follow this documentation for the installation. which will require the creation of metrics exporters, node exporters, scrape configurations, etc.
-
Ask HN: Best solution for homelab service monitoring?
Personally I use kubernetes, k3s is kind of lightweight, with the Prometheus operator.
https://k3s.io/
https://prometheus-operator.dev/
Kubernetes is not for everyone and is far from perfect but you already use Docker and you seem to seek many features offered by Kubernetes.
-
Opinions on using the Prometheus Operator vs. installing yourself?
I see that the operator is a community-run project. Does anybody have any experience (positive or negative) on running the operator itself? I wonder if it is more for multi-tenant Prometheus. For single tenant Prometheus collection, I guess the big gain is abstracting scrape config into ServiceMonitor and PodMonitor resources? Is there anything else that this makes much better?
-
Prometheus node exporter and cadvisor to send metrics to central prometheus cluster
But in all honesty if you’re on k8s you’re probably best served by the Prometheus operator. It’ll give you all that and more, easily.
-
Overcommitted cpu
Try some monitoring.
- What's your favorite monitoring stack?
-
Writing a Kubernetes Operator
It’s a common pattern [1] how else can users override the child objects you’re controller creates?
1 https://github.com/prometheus-operator/prometheus-operator/b...
-
Modify Prometheus rules when installed via Helm chart
The Prometheus operator is this one https://github.com/prometheus-operator/prometheus-operator
-
How do I stop my apps from being killed in k8s?
At a minimum, you want to look at your metrics using the Prometheus Operator. You can write alerts for resource requests.
-
Spring Boot monitoring with Prometheus Operator
Prometheus Operator is an independent project from the Prometheus project. I know, it can lead to confusion. In the official README you can find short comparison. Basically, Prometheus Operator does what an operator should do - provides Kubernetes native deployment and management of Prometheus and related monitoring components like Grafana or Alert Manager.
What are some alternatives?
cadvisor - Analyzes resource usage and performance characteristics of running containers.
kube-prometheus - Use Prometheus to monitor Kubernetes and applications running on Kubernetes
metrics-server - Scalable and efficient source of container resource metrics for Kubernetes built-in autoscaling pipelines.
mimir - Grafana Mimir provides horizontally scalable, highly available, multi-tenant, long-term storage for Prometheus.
php-fpm_exporter - A prometheus exporter for PHP-FPM.
kubernetes-mixin - A set of Grafana dashboards and Prometheus alerts for Kubernetes.
k3s - Lightweight Kubernetes
kuberhealthy - A Kubernetes operator for running synthetic checks as pods. Works great with Prometheus!
kubespray - Deploy a Production Ready Kubernetes Cluster
helm-charts - Prometheus community Helm charts
kube-metrics-adapter - General purpose metrics adapter for Kubernetes HPA metrics
prometheus - The Prometheus monitoring system and time series database.