Discovery keeps updating sensor values for Netscaler disk information

Hi,

We are monitoring Netscaler MPX units running NS12.0 (Build 51.24.nc) and at every discovery run, we see the following:

2017-09-26 06:34:29	System	Sensor Updated: netscaler-health Disk0Size Disk0Size
2017-09-26 06:34:29	System	Sensor Updated: netscaler-health Disk0Used Disk0Used
2017-09-26 06:34:29	System	Sensor Updated: netscaler-health Disk1Size Disk1Size
2017-09-26 06:34:29	System	Sensor Updated: netscaler-health Disk1Used Disk1Used
2017-09-26 06:34:29	System	Sensor Updated: netscaler-health Disk0Avail Disk0Avail
2017-09-26 06:34:29	System	Sensor Updated: netscaler-health Disk1Avail Disk1Avail
2017-09-26 06:34:29	System	Sensor Updated: netscaler-health Disk0Errors Disk0Errors
2017-09-26 06:34:29	System	Sensor Updated: netscaler-health Disk0Pusage Disk0Pusage
2017-09-26 06:34:29	System	Sensor Updated: netscaler-health Disk1Errors Disk1Errors
2017-09-26 06:34:29	System	Sensor Updated: netscaler-health Disk1Pusage Disk1Pusage

This is the case for all of our Netscaler units, but they are all running the same firmware version. These are also the only systems where we are seeing this behaviour.

I don’t know what could be causing this or where to check for sensor information, to compare values between each discovery and try to make sense of it all, so any help is appreciated!

Thanks!

NM. Please feel free to delete, as I wasn’t able to do it myself. Just realized my mistake in the fact that it’s the only “server” that we monitor and it’s normal to have those values updated. Bad morning!

Actually, to validate everything, I did the following test yesterday:
./discovery.php -h netscaler_host -d -m sensors

And I got the following information from the sensors:

sysHealthCounterValue.“Disk0Size” = 16858
sysHealthCounterValue.“Disk0Used” = 733
sysHealthCounterValue.“Disk1Size” = 158683
sysHealthCounterValue.“Disk1Used” = 11141
sysHealthCounterValue.“Disk0Avail” = 14776
sysHealthCounterValue.“Disk1Avail” = 134846
sysHealthCounterValue.“Disk0Errors” = 0
sysHealthCounterValue.“Disk0Pusage” = 4
sysHealthCounterValue.“Disk1Errors” = 0
sysHealthCounterValue.“Disk1Pusage” = 7

Now I ran is again this morning, and got the following values:

sysHealthCounterValue.“Disk0Size” = 16858
sysHealthCounterValue.“Disk0Used” = 733
sysHealthCounterValue.“Disk1Size” = 158683
sysHealthCounterValue.“Disk1Used” = 10920
sysHealthCounterValue.“Disk0Avail” = 14776
sysHealthCounterValue.“Disk1Avail” = 135067
sysHealthCounterValue.“Disk0Errors” = 0
sysHealthCounterValue.“Disk0Pusage” = 4
sysHealthCounterValue.“Disk1Errors” = 0
sysHealthCounterValue.“Disk1Pusage” = 7

So basically, the only values that changed were sysHealthCounterValue."Disk1Used" and sysHealthCounterValue."Disk1Avail". If that’s the case, is it normal that I still have all the events for the updated sensor values at every sensor pass?

Thanks again and sorry for the confusion!

Please pastebin the output of two consecutive ./discovery.php -h HOSTNAME -d -m sensors

1st discovery
2nd discovery, done a few minutes after the first one
3rd discovery, done right after the second one

Thanks

So those sensors shouldn’t be discovered as they are just disk space.

Try this patch:

https://p.libren.ms/view/raw/934d8764

Hi Laf,

Thanks for the patch. Indeed, there was no event log mentioning anything about the disks after applying it.

However, I also noticed that even with or without this patch, storage doesn’t actually seems to be tracked for those devices. It’s not in the dashboard of the device, nor is there any disk usage information in the “health” menu. Is this expected at this point?

Thanks again