sloth
kube-state-metrics
sloth | kube-state-metrics | |
---|---|---|
11 | 33 | |
1,949 | 5,102 | |
- | 1.2% | |
0.0 | 9.1 | |
2 months ago | 7 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.
sloth
-
SLOscribe: embed SLO/SLI into GO source code
It’s a CLI that allows developers to embed SLO annotation into GO code as comments and generate Prometheus alert groups when paired with Sloth, https://github.com/slok/sloth.
-
help setting SLIs/SLOs
SLOTH: https://github.com/slok/sloth
-
Observability Mythbusters: Yes, Observability-Landscape-as-Code is a Thing
Note: Although it’s outside of the scope of this post to dig deep into this topic, in case you’re curious, you can check out what an OpenSLO YAML definition looks like here.
- Pyrra v0.3.0 released
-
What you use for observability?
The actual hard part is standardizing all teams on SLI/SLO-based thinking. For that we're looking at tools like Sloth.
- How do you measure the reliability of a Kubernetes platform?
-
Calculating Remaining Error Budget
Have a look at sloth (https://github.com/slok/sloth) which will help you generate SLOs and error budgets given a PromQL query. This might be easier than trying to calculate it yourself. Plus, it's "metrics as code" and OpenSLO spec compliant.
-
openSLO
If you are in k8s and use Prometheus you could take a look at sloth: https://github.com/slok/sloth which can either generate the rules/alerts for you, or can run as an operator and allows you to write SLOs as k8s kinds.
-
SLI/Error Budget Calculators and management
Check out https://github.com/slok/sloth
- SLO calculation
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.
What are some alternatives?
pyrra - Making SLOs with Prometheus manageable, accessible, and easy to use for everyone!
cadvisor - Analyzes resource usage and performance characteristics of running containers.
slo-computer - SLOs, Error windows and alerts are complicated. Here an attempt to make it easy SLO Computer makes setting and monitoring SLOs for all your services intuitively seamless and blazingly fast. Community Support on Discord - https://discord.com/invite/Q3p2EEucx9
metrics-server - Scalable and efficient source of container resource metrics for Kubernetes built-in autoscaling pipelines.
kube-prometheus - Use Prometheus to monitor Kubernetes and applications running on Kubernetes
php-fpm_exporter - A prometheus exporter for PHP-FPM.
cloudprober - [Moved to cloudprober/cloudprober] An active monitoring software to detect failures before your customers do.
k3s - Lightweight Kubernetes
OpenSLO - Open specification for defining and expressing service level objectives (SLO)
kubespray - Deploy a Production Ready Kubernetes Cluster
mtail - extract internal monitoring data from application logs for collection in a timeseries database
kube-metrics-adapter - General purpose metrics adapter for Kubernetes HPA metrics