A tool to track SLA, SLO and Error budgets
A simple but effective way to track SLO's and Error budgets. SLO-tracker
can be integrated with few alerting tools via webhook integration to receive SLO violating incidents.
SLOs are a predefined approach to defining the amount of downtime that is acceptable for your product. Tracking SLO's and error budgets can be hard without proper tooling support because of the multitude of alert sources.
Since SLO's are directly related to the user experience of the product, more and more companies are defining their SLO's and tracking the error budget. Even though most monitoring tools provide SLO tracking feature out of the box, SREs don't find it to be a wholesome solution. This is because SREs might have different tools for monitoring different services and their respective SLIs.
In the event of an incident, manually aggregating these SLIs from multiple tools and placing it in one place to track error budgets is very challenging. Sometimes self-hosted monitoring tools might have short retention policies, thus making it hard to retain SLO metrics for longer durations(>6 months). And the most challenging situation is when false positive alerts reduce your error budget and you're grappling to gain valuable minutes into your error budget.
docker-compose up --build -d
admin:admin
is the default creds for UI, Which can be changed in docker-compose file.
SLO-tracker
from your monitoring tool defeats the purpose. Please send only SLO violating incidents to this tool.
Demo dashboard: http://demo.slotracker.com:3000/ (creds: admin:admin)
Blog: https://dev.to/squadcast/introducing-our-open-source-slo-tracker-a-simple-tool-to-track-slos-and-error-budget-4dp
Refer to CONTRIBUTING.md