Nagios 5.7.1 - BPI Inaccessible after apply config changes
Posted: Thu Jun 25, 2020 4:47 am
After migration to 5.7.1, we find out some strange behavior of Nagios and particularly BPI monitoring.
After apply new changes in configuration (host/service or so), Nagios shows 0 hosts and 0 services for some period of time, Nagios performs config’s refresh/reload or so....
During the time BPI starts sending alerts because essential hosts are unavailable, so all the big bosses concern about quality of their business services.
Is there any way to speed up data reload or change settings in BPI to recognize the data reload state?
For now, as workaround, we extend timeouts inside BPI and particular services, but in this way we slow down information flow for critical services
It's new behavior to 5.7.x (as we watch the graphs of availability), apply configuration changes in 5.6.x was transparent to BPI monitoring.
Darek.
After apply new changes in configuration (host/service or so), Nagios shows 0 hosts and 0 services for some period of time, Nagios performs config’s refresh/reload or so....
During the time BPI starts sending alerts because essential hosts are unavailable, so all the big bosses concern about quality of their business services.
Is there any way to speed up data reload or change settings in BPI to recognize the data reload state?
For now, as workaround, we extend timeouts inside BPI and particular services, but in this way we slow down information flow for critical services
It's new behavior to 5.7.x (as we watch the graphs of availability), apply configuration changes in 5.6.x was transparent to BPI monitoring.
Darek.