slo-tracker VS sloth

Hey all,

We are a small team and always struggled to track our product SLO's and Error budgets. So we wrote a small tool to track our product SLO, Error-budget, False positive incidents, and SLO burning rate. It also provides some analytics into how the team might have spent their error budget over time. This tool saved us a lot of time which we would have otherwise spent in aggregating SLO metrics from multiple places. Hope this will be helpful for some.

Currently integration with Prometheus, Pingdom, Grafana and Newrelic are supported. We are planning to add a few more integrations in the near future.

We'll be happy to get your feedback, suggestions and patches to make this a better tool for the community :)

Link to Github repo: https://github.com/roshan8/slo-tracker

Repo: https://github.com/roshan8/slo-tracker

[This](https://github.com/roshan8/slo-tracker) project is open-source. Feel free to open a PR or raise issue :)

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.

SLOTH: https://github.com/slok/sloth

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.

The actual hard part is standardizing all teams on SLI/SLO-based thinking. For that we're looking at tools like Sloth.

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.

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.

Check out https://github.com/slok/sloth