Nagvis chooses wrong icon for "service up but in downtime?"

[KDA]

This is a bit convoluted to explain, but please bear with me

I have a Nagvis map on which there is a host-icon. The host has a number of services assigned to it. All these services are in state "OK"/green, but one service is in scheduled downtime (dt). The host itself is OK/green btw. In this case Nagvis (IMHO) should select the icon "std_big_up_dt" for the host-icon (in effect green alarm-clock with a little green blob showing the underlying state pf the service) .... as everything is UP but there is at least one occurrence of 'something' which is in scheduled downtime. I have inspected the web page; the icon used is "std_big_up", i.e. no alarm clock.

By analogy: if the same service (which is in downtime) is in a WARNING state, the host icon changes to "std_big_warning_downtime" (=green alarm clock with the little yellow blob showing the underlying state).

Why IS there a "std_big_up_dt" icon if it is not used in precicly this situation?

Am I misunderstanding something?

[benjaminsmith]

Hi,

Thanks for contacting the Nagiso Support team.

After looking over the description,it does look like an issue/bug in NagVis since it's not displaying the correct icon given the current status. NagVis is actually a community project included with Nagios XI, I would recommend opening an issue on the GitHub repo for review by the developer.

https://github.com/NagVis/nagvis/issues

Benjamin

[KDA]

Hi

I did re-post the question to the nagvis issue board you referred to... but sad to say it has not caused an avalanche of responses

I am not really sure how to proceed.... as nagvis is a community effort, should I try to fix the issue myself and simply commit it?... but if so, what happens next... will it be taken in a Nagios release at some point?

regards
Håkon

[benjaminsmith]

Hi Håkon,

I would give it a little more time since it's a community project. Have you been able to locate the issue in the source code?

We do update this but there is a lag between the version included in XI and the latest. We are currently using 1.9.8. However, if this is a minor change you could update the file locally (have to be careful with XI upgrades as those changes may be overwritten).

--Benjamin