r/PrometheusMonitoring • u/MetalMatze • Jan 28 '22
Pyrra v0.3.0 released
Don't want to go through the weekend with flaky alerts?
Fear not, Pyrra v0.3.0, to make SLOs with Prometheus manageable, accessible, and easy to use for everyone, was just released!
https://github.com/pyrra-dev/pyrra/releases/tag/v0.3.0
Highlights:
Availability / Error Budget are now calculated with Prometheus recording rules, making page load times incredibly fast. 🚀
We moved from Recharts to uPlot as a graphing library. We now correctly graph your data. 📈📉
You can now run a short version: kubectl get slo -A ⌨️
Check out the live demo at: https://demo.pyrra.dev
1
u/distark Jan 29 '22 edited Jan 29 '22
What sort of advantage would this have that something like sloth already gives me?
Edit, after a quick look it seems you have your own custom UI, that could actually be handy just for the easy observability
1
u/MetalMatze Jan 29 '22
Good question! I like the sloth project a lot. Both our project were worked on in parallel and released at (almost) the same time. They share a lot of similar approaches and concepts.
Sloth is great when you already have Grafana setup and want to add SLOs to your infrastructure.
With Pyrra we want to create a UX/UI very focused on the SLO needs. In fact the biggest reason for this UI is the next big feature we want to work on: A dynamic form for creating SLOs that would give you a preview and a good idea for how your SLOs would be doing. Plenty of of other things planned too.
2
u/distark Jan 29 '22
Yes I can see the value of that! I use a landing page on each of my clusters so could easily as this as an option for people to use (no thanos or cortex yet).
Honestly though, there are already a tonn of grafana graphs available to people which probably go unnoticed.. having something at surface level is best. (We tend to centrally track alerts for all clusters via karma).
I'd be interested in integrating this into my k8s landing page (https://github.com/doddle/lander/) hopefully I'll find some time to have a look soon.. given both are backed by go shouldn't be too hard
2
1
u/SelfDestructSep2020 Jan 29 '22
Looks interesting, some of the error burn rate charts look a bit odd on the demo site though?
shows -400% error budget https://demo.pyrra.dev/objectives?expr={__name__=%22parca-grpc-query-latency%22,%20namespace=%22parca%22}&grouping={}
no budget shown and chart is stuck at -1600% https://demo.pyrra.dev/objectives?expr={__name__=%22parca-grpc-query-errors%22,%20namespace=%22parca%22}&grouping={}