check_postgres.pl from Bucardo Loves Open Source
It is the one-stop shop for monitoring PostgreSQL. Each time I need to monitor some new aspect of PostgreSQL, this perl script has the method available.
1 Like
One thing that I could really use is the ability to not send notifications when I set Downtime. Definitely default to sending notifications, but having the ability to disable sending is what I want.
For Host Downtime I would also like the ability to just disable sending notification for “All Services” separate from the host notification control. IE: Allow host notifications to be sent but disable all service notifications from being sent. Also flow these settings onto Child hosts if that is selected as well.
The problem is for a host with a lot of services being monitored, enabling the All Services slider generates a lot of emails/alerts. That in most cases I do not need to see.
So if a couple of extra controls can be added to the Downtime screen to allow this, would be most appreciated.
2 Likes
Yes, this would be great, as I resorted to just disable all Downtime related messages in the notification filters.
Are these polls closed? I find the documentation a bit scattered, poorly defined, and out of date without clear messaging of being so. You have an official old guide on the website, and a magically more informative guide on GitHub. How about a last updated date? I wanted to see which OS would be ideal to use Icinga2 on so I tried a few. Though the best route is to check Icinga repos to see which gets updated most often. Looks like Ubuntu is the way to go.
As someone who is adopting Icinga2, I cannot tell you how infuriating it is to Google a question, only to end up in this community with an employee replying to someone with the same question with a generic link to the main website or a “we don’t write a guide” and then closing the thread.
Imagine the place where this product should have the best community support actually is just a dead end and we’re better off on Stack Exchange.
Hello,
yes the polls were part of a yearly week long event - but we are of course always open to feedback!
Our docs are rendered every night, so they should match what you see on github for the latest version. The main branch on GitHub is ahead of the last release, so the differences you noticed might be due to that.
I don’t think that there is a lot of difference between the different distros you can run Icinga on, the frequency of updates is mostly due to dependencies that need to be updated that come in, and not a sign of an OS getting better care or support than others. All of the distros that we list as supported are up to date.
As someone who has been working on and with Icinga for a while now, my perspective and way of looking for answers is probably very different from yours, and I think I have lost touch with what it is like to just start out.
If you have any examples or suggestions for me to look at, please send them my way. Constructive criticism is something I’m always happy to receive and pass on to the devs that can do something about it!
1 Like
Thanks for the response.
I would invite you to use your own installation manual for Ubuntu to install a functioning Icinga2 and Icinga2 Web. Using, say, Postgresql and Nginx (not a requirement ) and do not do anything outside of what the installation tells you to do.
I don’t think you would succeed to reach a setup page. If you improvise and reach setup, I think you will be confused when it comes time to fill out the form information. A bit easier if you use MariaDB… But only because you already know what it’s looking for. Look at the final few steps of the Icinga Web guide. Do they feel in order? Do they feel like the same person that wrote the Icinga 2 page?
You’ve got a DB Resource that is looking for IcingaDB and an Icinga DB Web looking for Icinga DB Resource. Cue spidermen all pointing at each other.
I mean, it’s as simple as that. Look at what other Icinga installation docs have. They provide information everyone is looking for because it’s not in the main doc. Labeled better because the way it’s originally written is confusing. I could go into far more detail but I’m hoping if you try to skim through with fresh eyes you could see what I and likely many frustrated others see. Postgres character set has to be edited. Even after all that, you would arrive at a broken dashboard filled with php errors. Thanks again.
1 Like
I’m monitoring memory usage on my NixOS build server using the Linuxfabrik plugin. Nothing special on its own…
But!
This service has a Dependency which disables checks as long as there’s an “ld” process (procs, crit=0). Useful as I know linking Linux is expensive and don’t want a notification every time… 