gatus VS go-multierror

Official support in healthchecks.io, Uptime Kuma, Radarr, Sonarr, Shoutrrr, Gatus, and many more!

I moved to (Gatus)[https://github.com/TwiN/gatus] for this reason. All defined in a yaml config file.

Gatus IMO is better suited. Here's the Github repo.

If you want to self-host, https://github.com/TwiN/gatus. If you want a managed service, https://gatus.io

We use a self-hosted Gatus at work: https://github.com/TwiN/gatus

Maybe take a look at gatus instead.

If you want more of a 1:1, this is what I found when I was looking for an alternative a while back. https://github.com/TwiN/gatus

Some packages offer utilities to gather results from goroutines, such as multierror.Group or parallel.Map in samber/lo.

I've created a simple Go library for managing concurrent tasks, results, and errors. Inspired by HashiCorp's go-multierror, it simplifies running goroutines, collecting results, and error handling by minimizing boilerplate code.

This looks great and can be integrated into ORM. What about adopting go-multierror?

Unlike errgroup, github.com/hashicorp/go-multierror cannot be interrupted by context. However, it is useful for use cases where you need to check all errors and handle them carefully, because you can keep all errors.

I found that it was also useful to introduce https://github.com/hashicorp/go-multierror so if one or more single work items returns an error, we can also batch the errors as a single thing.