sloth
sloscribe
| sloth | sloscribe | |
|---|---|---|
| 11 | 3 | |
| 1,949 | 29 | |
| - | - | |
| 0.0 | 7.9 | |
| 2 months ago | 5 months ago | |
| Go | Go | |
| Apache License 2.0 | MIT License |
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
sloscribe
-
SLOscribe: embed SLO/SLI into GO source code
Hi everyone! Hope you’re doing well! I’ve been working a small side project, https://github.com/slosive/sloscribe and I figured this might be a good place where to post it!
-
Slotalk: embed SLO/SLI specification within source code
I've been working on a small side project link https://github.com/tfadeyi/slotalk.
What are some alternatives?
pyrra - Making SLOs with Prometheus manageable, accessible, and easy to use for everyone!
prometheus - The Prometheus monitoring system and time series database.
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
nightingale - An all-in-one observability solution which aims to combine the advantages of Prometheus and Grafana. It manages alert rules and visualizes metrics, logs, traces in a beautiful web UI.
kube-prometheus - Use Prometheus to monitor Kubernetes and applications running on Kubernetes
sensu-go - Simple. Scalable. Multi-cloud monitoring.
cloudprober - [Moved to cloudprober/cloudprober] An active monitoring software to detect failures before your customers do.
easeprobe - A simple, standalone, and lightweight tool that can do health/status checking, written in Go.
OpenSLO - Open specification for defining and expressing service level objectives (SLO)
coroot - Coroot is an open-source APM & Observability tool, a DataDog and NewRelic alternative 📊, 🖥️, 👉. Powered by eBPF for rapid insights into system performance. Monitor, analyze, and optimize your infrastructure effortlessly for peak reliability at any scale.
kube-state-metrics - Add-on agent to generate and expose cluster-level metrics.
mtail - extract internal monitoring data from application logs for collection in a timeseries database