Hi all,

In order to get the monitoring queries have a less impact in other transactions in terms of locking and blocking, I have been setting the TRANSACTION ISOLATION LEVEL by modifying the centreon's code.

I have been using the code modified successfully, mitigating blocks issues in databases of intensive use.

I think it will be a good enhancement to include this options in the mssql c

Currently the warning and critical threshold trigger when the number of nodes is above the number set in the threshold. They should trigger when the number of nodes goes below the threshold.

# ./check_rabbitmq_cluster -w 2,2 -c 1,1
RABBITMQ_CLUSTER CRITICAL - nb_running_node CRITICAL (3) nb_running_disc_node CRITICAL (3), nb_running_ram_node OK (0)
# ./check_rabbitmq_cluster -w 4,4 -c 

Hi

Just a suggestion.
For beginner, "okconfig addtemplate" is confusing.

According to folloiwng, it's action is to apply a existing template onto a host.

okconfig addtemplate <host_name> --template oracle

addtemplate should reserved for adding a new template not existed in /usr/share/okconfig/templates dir.

Existing "okconfig addtemplate" should be "okconfig applytemplate

https://www.claudiokuenzler.com/nagios-plugins/check_esxi_hardware.php
"If no hw/vendor type was given, unknown will be used (like auto)"
In fact auto autodetects/selects a vendor name if it can, which unknown doesn't.

Also is there any reason unknown is the default rather than auto? Changing this would allow it to return more info by default (especially on HP), then you could switch to unkno

Issue Type

Bug report

Issue Detail

• check_netapp_ontap version:
• NetApp Ontap version:
• Monitoring solution: Centreon / Centreon-Broker

Expected Behavior
No bug in check snapshot_health if volume is 0 sized

Actual Behavior
Illegal division by zero at check_netapp_ontap.pl line 1464

How to resolve Behavior
at line 1458 add space-total condition :

%centreon_vmware_config = ( port => 5701, vsphere_server => { 'default' => {

is not the same as

%centreon_vmware_config = ( port => 5701, vsphere_server => { 'DEFAULT' => {

I believe these should be case insensitive.
I believe the behavior of the config being case sensitive is contraintuitive.

root@diskmaskin01:~ # /usr/local/libexec/nagios/check_zpools.sh -p thispooldoesnotexist ; echo $?
cannot open 'thispooldoesnotexist': no such pool
cannot open 'thispooldoesnotexist': no such pool
/usr/local/libexec/nagios/check_zpools.sh: line 125: [: !=: unary operator expected
ALL ZFS POOLS OK (thispooldoesnotexist)|thispooldoesnotexist=%
0
root@diskmaskin01:~ #