nagios

Since your apps are containerized it easy to monitor them for resource usage, hook it to nagios etc.

You could probably easily plug this into Nagios and it's dependency rulework can figure out who to page when.

Negative, but sc ollector can use external scripts, but they are not in the nagios format.

I mean, the solution works, but due to Nagios it's inherently hacky.

Site Reliability -- one for nagios alerts, one for site testing, one for munin, and one for github PRs 5.

Aside from some crappy pre- and post-upgrade scripts, it works remarkably well, and is compatible with the Nagios monitoring plugin ecosystem.

I used Nagios for years but it never evolved past a bunch of CGI scripts written in C(!).

In my org we ended up choosing another nagios replacement, but not because of any flaw in bosun.

The collector OS agent is windows compatible and backwards compatible with nagios scripts.

If it isn't, start up nagios locally based on the latest sync'd statefile.

It's bizarre that Nagios doesn't (didn't?) have inbuilt support for failover this way.

Because that's what Nagios is, not the default checks it ships with.

So other than "it does alerting" it is a very different beast from Nagios.

Bosun really is different in many ways than Nagios.

I saw an absolutely crazy way to do this with Nagios[1].

Nagios saves its state in a file, and the suggested way to synchronise two separate systems was to have them look to see if the other one is active.