SLOs should be easy, say hi to Sloth

As in other areas, in the technology world, every year there are some buzz words that are being said more than others. Some examples: <ul> <li>2017: Cryptocurrency and blockchain</li> <li>2018: Observability and tracing</li> <li>2019: Service mesh</li> <li>2020: Gitops</li> </ul> And this year, the fancy word is SLO. I’m sure you have been hearing service level objectives lately (not only because of the <a href="http://sloconf.com/" rel="noopener ugc nofollow" target="_blank">SLOConf</a>). SLOs aren’t new, and most likely that if you are reading this, you are already familiar with SLI, SLO, SLA, error budgets… lingo. Apart from the buzzword, SLOs are awesome, and if you are not using them at this moment, explore them if you can, because I’m sure that you will get value from them. Now I’ll talk about how I end up implementing <a href="https://github.com/slok/sloth" rel="noopener ugc nofollow" target="_blank">Sloth</a>, so you can skip directly to <a href="https://slok.medium.com/slos-should-be-easy-say-hi-to-sloth-9c8a225df0d4#4b95" rel="noopener">Sloth section</a> if you want. <a href="https://itnext.io/slos-should-be-easy-say-hi-to-sloth-9c8a225df0d4">Website</a>