Unrecognized Disk Usage Metrics [ Metrics GUI Broke ]

[jackuna]

2018-01-22 14_57_13-Nagios XI .png

2018-01-22 15_02_14-Nagios XI .png

Hello All,

I couldn't even figure out how do i ask the issue as it's a kind of strange issue.
But I'm trying my best to explain it.

We are running NagiosXI Ver 5.4.11 on a Linux Box, we are using SNMP agents to check windows services and drives status.
Here the error comes only while adding F Drive [ 2 TB ] disk usage check.

Every thing seems to be fine while adding and looking into host and it's service, but when i check Metrics menu Disk Usage, it gives a irrelevant figure and graph, and it's only after addition of F Drive usage check.

please have a look on the attachments, it will surely help to understand my issue.

Thanks in Advance.

[dwhitfield]

You say the UI is broke. Can you show the output from the command line?

Also, what's the output of the following:

Code: Select all

snmpget -v1 -c public server 1.3.6.1.2.1.25.2.3.1
snmpget -v1 -c public server 1.3.6.1.2.1.25.2.3.1.5
snmpget -v1 -c public server 1.3.6.1.2.1.25.2.3.1.6
snmpget -v1 -c public server 1.3.6.1.2.1.25.2.3.1.4

Change the version community string as necessary. Also, can you provide a link to that plugin? I can search for it by name, but people can name plugins whatever they like, so I want to make sure I am looking at the correct plugin.

[jackuna]

Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: HOST-RESOURCES-MIB::hrStorageAllocationUnits


This one is the common output for every changed MIB when run from the CLI.

And I have not renamed or created any plugin.. all are the default plugins used by NagiosXI for Windows host monitoring from SNMP through Config Management GUI tool

[dwhitfield]

Just so I am sure of what I'm working with, what's the output of:

Code: Select all

/usr/local/nagios/libexec/check_snmp_storage.pl --version

[jackuna]

check_snmp_storage version : 1.3.3

[dwhitfield]

Here the error comes only while adding F Drive [ 2 TB ] disk usage check.

So far I'm not seeing anything to explain the above. It seems like SNMP is not set up correctly, but I don't have a ton of info right now. We definitely need a deeper dive. To that end, can you PM me your Profile? You can download it by going to Admin > System Config > System Profile and click the ***Download Profile*** button towards the top. If for whatever reason you *cannot* download the profile, please put the output of View System Info (5.3.4+, Show Profile if older) in the thread (that will at least get us some info). This will give us access to many of the logs we would otherwise ask for individually. If security is a concern, you can unzip the profile take out what you like, and then zip it up again. We may end up needing something you remove, but we can ask for that specifically.

You can also generate a profile manually using the script at /usr/local/nagiosxi/html/includes/components/profile/getprofile.sh

That should generate a profile in /usr/local/nagiosxi/var/components/ which you can get off the server with an application such as FileZilla.

After you PM the profile, please update this thread. Updating this thread is the only way for it to show back up on our dashboard.

If you get an error that PROFILE BUILD FAILED, please see https://support.nagios.com/kb/article.p ... ategory=44

[jackuna]

I have private messaged you.

[tacolover101]

this looks like a bug where the metrics component is pulling the ram #, rather than doing the calculation.

the 'metrics' page does not always calculate properly, as it only accounts for so many types of formats of data i believe.

[jackuna]

So what I'm supposed to do with it, shall i open a Nagiosxi Customer Support ticket for it, what do you suggest.

There are many disks of sizes in Tera Bytes which i need to monitor in Disk Usage metrics, i can not ignore it at all.
It gives a bad impression of my dashboard.

[dwhitfield]

this looks like a bug where the metrics component is pulling the ram #, rather than doing the calculation.

The problem is your actual SNMP check is showing negative usage, which is not accurate. That's the issue that needs to be resolved. It's true that the metrics component could handle this better, but that's not the real issue.