NagVis Hard State Monitoring Issue

nagvis
php
nagios-plugins
(Ash) #1

Hi All,

I’m having issues with NagVis displaying critical state icons for Hosts & Services with an “OK” hard state when toggling on the “only display hard state option”.

For example in Nagios a printer is in the state below,

Current Status: OK (for 0d 4h 1m 13s)
Status Information: OK - xx.xxx.xxx.xxx: rta 26.113ms, lost 0%
Performance Data: rta=26.113ms;8000.000;9000.000;0; pl=00%;80;95;; rtmax=26.113ms;;;; rtmin=26.113ms;;;;
Current Attempt: 1/6 (HARD state)
Last Check Time: 01-24-2019 12:53:01
Check Type: ACTIVE

On the NagVis map the summary state is “Critical” and the summary output set to “OK”.

Any ideas why they are displaying this way? My Version details are as below;

Nagios® Core™ 4.4.1
NagVis Version 1.9.10
PHP Version 5.4.16
Apache/2.4.6 (CentOS)

#2

Please show the backend definitions of nagvis.ini.php.

(Ash) #3

Hi Wolfgang,

I’ve made no changes to the nagvis.ini.php since install. All lines in the backend section appear to be still commented out.

I have also noticed this only seems to affect service icons and not host icons.

; ----------------------------
; Backend definitions
; ----------------------------

; Example definition of a livestatus backend.
; In this case the backend_id is live_1
; The path /usr/local/nagios/var/rw has to exist
[backend_live_1]
backendtype=“mklivestatus”
; The status host can be used to prevent 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>:” -> e.g. “live_2:nagios”
;statushost=""
;socket=“unix:/usr/local/nagios/var/rw/live”

; Example definition for a MySQL backend
; in this example the ID of the Backend is “ndomy_1” you can define another ID.
[backend_ndomy_1]
; type of backend - MUST be set
backendtype=“ndomy”
; The status host can be used to prevent 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>:” -> 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=“root”
; password for NDO-db
;dbpass=""
; prefix for tables in NDO-db
;dbprefix=“nagios_”
; instance name for tables in NDO-db
;dbinstancename=“default”
; maximum delay of the NDO Database in seconds
;maxtimewithoutupdate=180
; path to the cgi-bin of this backend
;htmlcgi="/nagios/cgi-bin"

Thanks

#4

Meaning there is at least one not-OK service changing the summary state when you toggle the setting?

(Ash) #5

No All the services on the host are in an OK “Hard State” in Nagios however toggling on the “Show only Hard States” option changes the services to critical.

Thanks