3 ms·
We use Icinga2, after having used Nagios previously. Icinga2's configuration files are a joy to use when compared to Nagios, and the interoperability with Nagio
by falcolas 12y ago
We use Icinga2, after having used Nagios previously. Icinga2's configuration files are a joy to use when compared to Nagios, and the interoperability with Nagios Plugins is really nice.
On the other hand, we're getting really sick of every upgrade breaking our environment (if it's not the post-install scripts choking on our use of a non-default DB name, it's the configuration parser choking on previously-valid configuration files, or...), and we wish that the new UI could catch up with the capabilities of the classic UI.
We also wish we could pin a package version, but the Icinga devs remove the previous version from their repo the moment the new package goes up. Our solution to this will be to host the truncated packages on our own repo; we just wish we didn't need to do that.
- erikb 12y agoI had the same problem with other projects like that before. We were lucky on finding older builds in some Linux distribution repo. Maybe you can also try looking in Suse's or Debian's repos for them. Another, often used alternative is automatically building an open source project for yourself. Especially if you find that new versions build your system on a regular basis. Building it yourself is the first step to get involved in the release process.