Phoenix (Update, stabilize, release, 🚀)

[slok]

It has taken me a while to find a bit of motivation and energy again, so thank you @fiunchinho for the kind words, they really helped. ❤️

Maintaining open source can be hard, especially when the human side gets lost and contributions are treated like a company service rather than a shared effort of culture and innovation. Over time, that dynamic made it hard for me to stay engaged, and honestly, it became overwhelming.

Sloth is stable and near feature complete, however I will try my best on the next iterations. I cannot promise constant updates, but I’ll try to get back into it with clearer boundaries and expectations. This is a personal project, not something backed by or built for a company 😄, so I’ll be doing what I can, when I can.

Thanks to everyone who’s been patient and kind along the way.

Update tasks

• Go (1.24) -> Update Go, Kubernetes, CI and deps #546
• Kubernetes (1.32) -> Update Go, Kubernetes, CI and deps #546
• Prometheus -> Update Go, Kubernetes, CI and deps #546
• Rest of dependencies
  • Update Go, Kubernetes, CI and deps #546
  • Update helm test dependencies #552
• CI -> Update Go, Kubernetes, CI and deps #546
• Docs
  • Update project and links -> Update website sloth-website#24
  • Readme with status -> Update CI and some docs #548
• Deployment resources (Helm, kustomize)
  • Git sync -> Update deployment manifests Git-sync from v3 to v4 #554
• Common SLI plugins -> Update deps sloth-common-sli-plugins#85
• Grafana dashboards
• Github
  • Label PRs
  • Label Issues
  • Setup discussions
• Release 🚀
  • Sloth -> Prepare v0.12.0 release #555
  • Deployment manifests -> Prepare deployoment manifests release for v0.12.0 #556

[slok]

New image available if any one wants to test and share the results:

docker pull ghcr.io/slok/sloth:7b4010fe050109d7372ae584d92aea0cce33cf29

[cxdy]

Thanks for everything Slok! Glad to see you're back.

[aka-switch]

It's good to see you back! Is it possible to add Victoria metrics support as it was done in the fork from ostrovok tech? I can bring a PR.

[slok]

Hey @aka-switch, thanks!

I’m currently catching up and figuring out how to onboard all the recent developments. The two-year gap in Sloth’s maintenance led to several company-specific forks, each adapting the project to different needs. That ended up being valuable, as it showed how various organizations approach SLOs. Google's model is a solid starting point, but in practice, each context needs its own tweaks.

Sloth’s original goal was to make SLOs simple and easy to use. With that in mind, I’ve been thinking about how to make Sloth even more pluggable, similar to what we did with SLIs, which worked quite well. The idea is to keep the core clean and lightweight, while allowing custom SLO logic to live in separate modules, with their own lifecycle and maintainers.

So regarding VictoriaMetrics, yes, I think it would be great to support it. But I’d prefer to hold off until I have a clearer idea of how to structure and refactor the plugin system properly.

Thanks for your patience, and for continuing to help make Sloth better!

[aka-switch]

Thanks, @slok. Let me know if you need any assistance later. I'll be glad to help you with the integrations.

[slok]

👋 Finally it's here, a new release, mainly maintenance changes: #557

[slok]

Some of the tasks in the list will be postponed until the next Sloth release, which will be a big one including a whole Sloth app refactor and the new SLO plugin system. From my side, I’d consider this issue resolved, the project is finally getting back on track 🚀.

Once again, huge thanks to everyone who has been supportive and kind all this time.

[fayak]

Thanks for the efforts @slok !
Really appreciate it :)