Nagios Support Forum

xi 5.2.8
We have Network Analyzer integrated with Nagios xi, and have used the Nagios Network Anlyzer wizard to initiate checks on the NNA server.

About 35 days ago, the NNA box was rebooted to add more memory, and when it came up, unbeknownst to us, firewalld autostarted. This blocked all inflows to NNA.

Fast forward to today when we log into the box to troubleshoot a production issue and find no data for 35 days. Not understanding why we didnt get alerts for this, I check xi and find that the byes, flows, and packets are all reporting 0 sent/received, but are in an OK state. The plugin thought that 0 traffic in/out was ok.

I checked the plugin and did not find any option to specify any warning or crit threshold for low numbers, which I was expecting because the wizard didn't seem to offer that option either.

Can this check be altered to allow for 0 bytes of in/out of flows, packets, and bytes not be an OK state?

I've attempted to reproduce here and so far I can answer only part of your question, which is how to set the warning/critical threshold when values are equal to or less than?
On NNA this is easy. For the Alert, just put : immediately after the value - see screenshot. Now on xi, what wizard did you use? Let me know and I can continue to troubleshoot, thanks --

I used the Nagios Network Analyzer wizard that comes stock with xi.

Ok, the Network Analyzer wizard in xi only supports above value thresholds at the moment - this is why you were not alerted on 0 bytes transferred.
I have submitted a feature request that xi's NNA wizard support below value thresholds - TASK ID 8842

In the meantime, if you want to be alerted on 0 bytes or 'near zero' bytes transferred, you'll have to configure such on NNA, as mentioned in my previous post.

Thanks for adding the feature request, hopefully it's quick and easy to implement. I will see about adding that check in NNA in the meantime. You can lock this topic.

No problem -- To be honest I don't know if or when it would be implemented, as that is dev's call to make, but I've seen a few requests for 'below value threshold' alerting previously so it seems like the demand is there.
I'll close this one out now....