One last question, as we haven't been able to reproduce this behavior reliably yet, does it make sense to create the Github issue now? Or would you want me to hold off on that until we've put the time in to create a lab setup? (to which I must confess,…
During office hours I don't mind turning off notifications, we still have Icinga Web 2 that we can watch. But it's not something we can do all day.
With notifications turned off via "icinga2 feature disable notification" there are indeed no queries to…
After reading the first line in your previous post I feel a little guilty that I wrote bdr in lower case in my first post. My apologies for that, you've been a great help so far and I should have made the bdr more obvious.
Theoretically, the bdr could…
Thanks again for your in-depth response!
I've written a quick script to analyse the debug log (see attachments for both the script and the output).
Our postgres bdr is running on the same host (both on the Icinga2 master and on the Icinga2 client).…
A sample of a notification scheme for one particular service:
Object 'cap1!load!call-noc-service' of type 'Notification':
Object 'cap1!load!callsms-l1-daytime-service' of type 'Notification':
Object 'cap1!load!callsms-l1-night-service' of type…
Most check-intervals are at 120, many are at 300, some are more, we're averaging at 135 for active checks. The retry_intervals are mostly at 30, we're averaging at 47 there. Notification intervals are at 300.
Please see the attachments for config of…
Thank you for your response.
Since your answer yesterday I've upgraded to the 2.7.2-1.jessie packages and put monitoring on the Postgres database. The only two databases in this Postgres instance are those for Icinga2 and Icingaweb2.
What I see when…
I manage a monitoring setup running Icinga2 version r2.6.3-1 (from the 2.6.3-1~debmon8+1 debian package) in a 2 node master-client setup with 153 hosts and 1456 services on a postgresql bdr database.
After the icinga2 process is started or…