Nagvis blue screen icon after apply configuration

[progressive.nagiosXI]

Hi Team,

we created different Nagvis monitoring dashboard for all of our clients .

The problem is when we do changes all day in Nagiosxi as per different client requirement ,adding/deactivating /change threshold values of servers and do apply configuration,the result is that after apply configuration Nagvis show blue screen for 2-3 minutes due to which our clients frustrate on us.

Please help us what to change in settings/configuration so that other client Nagvis not affect after apply config.

Note:-This is drawback of Nagvis to show blue icon,this need to be done on background.

Thanks

[npolovenko]

Hello, @progressive.nagiosXI. Can you send us a screenshot of a blue screen caused by Nagvis?

Also, next time when you see a blue screen please generate and send us your system profile.
Login to the Nagios XI GUI using a web browser.
Click the "Admin" > "System Profile" Menu
Click the "Download Profile" button
Save the profile.zip file and send it to me in a private message.

Archive recieved and shared with the support team.

[progressive.nagiosXI]

Hi

Details has been shared in PM

Thanks

[ssax]

The backend isn't ready until then so you'll continue to see that because nagvis relies on the ndo backend.

You may be able to enable Admin > Performance Settings > Backend Cache and that should cause it to work but that wouldn't be live data in the XI interface OR the nagvis interface. (I haven't tried this and I'm leaving for the day).

I don't see any nagvis cache specific settings either so we'll need to work with what we got.

What version of XI are you using so that I can look at the proper nagvis version to see if we can come up with a solution.

[progressive.nagiosXI]

current version :- Nagios XI version: 5.6.2

Admin > Performance Settings > Backend Cache == >> not solving problem

@Team you need to add this feature in upcoming nagios/nagvis versions

what we want is
After apply config == > some triggered occur ==> Nagvis polling stop for 2-3 minutes till nagios restart and update data properly.
(Nagvis freeze for 2 minutes untill all ok)

[ssax]

Try editing this file:

Code: Select all

/usr/local/nagvis/etc/nagvis.ini.php

And under this section, uncomment ; maxtimewithoutupdate=180 and see if that fixes it:

Code: Select all

[backend_nagiosxi]
; type of backend - MUST be set
backendtype="ndomy"
; The status host can be used to prevent annoying timeouts when a backend is not
; reachable. This is only useful in multi backend setups.
;
; It works as follows: The assumption is that there is a "local" backend which
; monitors the host of the "remote" backend. When the remote backend host is
; reported as UP the backend is queried as normal.
; When the remote backend host is reported as "DOWN" or "UNREACHABLE" NagVis won't
; try to connect to the backend anymore until the backend host gets available again.
;
; The statushost needs to be given in the following format:
;   "<backend_id>:<hostname>" -> e.g. "live_2:nagios"
;statushost=""
; hostname for NDO-db
;dbhost="localhost"
; portname for NDO-db
;dbport=3306
; database name for NDO-db
;dbname="nagios"
; username for NDO-db
dbuser="ndoutils"
; password for NDO-db
dbpass="n@gweb"
; prefix for tables in NDO-db
;dbprefix="nagios_"
; instance name for tables in NDO-db
dbinstancename="localhost"
; maximum delay of the NDO Database in seconds
maxtimewithoutupdate=180
; path to the cgi-bin of this backend
;htmlcgi="/nagios/cgi-bin"

[progressive.nagiosXI]

Hi
Changes done,
Observed 2 days ,issue still not resolved.

Thanks

[tgriep]

If it takes the serve 3 to 4 minutes to update, then you will have to increase the maxtimewithoutupdate to a larger value so it will wait long enough before getting the status update for the Nagvis objects.

One more thing, in the Nagvis menu, go to the Options > General Configuration menu and increase the refresh time to a larger value as well.