Hi @Farzana-HUBONE, Please ask your problem in English. This will help all other non-french speaking users who have the same issue to benefit from the solutions that will be proposed. Thank you for your understanding : )

Hello @Fabrix, 

I understand the purpose so here :

We use the QNAP monitoring plugin and we are facing 2 issues :

• The metric unit associated to the service Volume - monitoring the Disk usage - is by default GB, but the data collected are actually in TB/To (values are OK, unit is NOK)
  => Where could we modify the unit set by default ?
• The Hardware-Global service which has among its options --component='.*' seems to requiere the knowledge of the host MIB
  - Am i right ? ?
  It has the status   UNKNOWN   :
  => Why can it not find the MIB tree ?
  => How to communicate it the MIB ?

Advance thanks for your replies,

FM

I’m just answering for the

“The Hardware-Global service which has among its options --component='.*' seems to requiere the knowledge of the host MIB
- Am i right ? ?”

no

if you do a “--help” on the check you get the component information

    --component
            Which component to check (Default: '.*'). Can be: 'disk', 'fan',
            'mdisk', 'psu', 'raid', 'temperature'.
 

if you want to filter specific object add a --filter

    --filter
            Exclude some parts (comma seperated list) (Example:
            --filter=disk) Can also exclude specific instance:
            --filter=disk,1
 

if you are not sure of the number to put after disk for example it’s the instance number, you get it by doing a --verbose on your check, this will list whatever you have on your qnap

you don’t need mib knowledge or file HOWEVER : you need to setup your snmp correctly on your qnap (the correct community and snmp version, I would advice snmp v2 to start checking before going into v3, this will help you debug more easily) 

for the snmp error if someone has more information on the QNAP mib : the information is stored like this in the qnap, in 2 different place : 

one is text string, so unusable as is

the other has number, but this is in “Kilo Bytes” apparently

(there is a third place it’s in the centreon plugin, but it returns the samed thing as the 2nd one)

personnaly I don’t care about the absolute volume size, what I care about is % usage/free, I realized just now that all my qnap display GB instead of TB, and no one noticed! (for the last 2 or 3 years haha)

@christophe.niel-ACT 

Thank you for your reply, it help me understand the purpose of the service and bring a solution by duplicating this service as many times as there are types of component.
I had to add the option --snmp-timeout=5 as the timeout was 1 second by default, not enough to get all informations about the disks in my case.

personnaly I don’t care about the absolute volume size, what I care about is % usage/free, I realized just now that all my qnap display GB instead of TB, and no one noticed! (for the last 2 or 3 years haha)

As I understand the logic i don’t pay attention to the Unit either, but the client to whom belongs the NAS cares.

I tried to use the options --change-short-output --change-perfdata, I probably don’t know how to parameter them so still on it.