IMPROVE : alert of some plugins doesn't triggers notifications

[algorys]

Hello,

I've noticed that some commands who changes to WARNING or CRITICAL doesn't triggers notifications. I'm not sure that's part of monitoring plugin or Shinken issue...

--> Here is some example :

SERVICE ALERT: routeur;currentconnections;CRITICAL;HARD;3;SNMP CRITICAL - 1098

Corresponding command :

./check_snmp -H $HOSTADDRESS$ -c public -o .1.3.6.1.4.1.8741.1.3.1.2.0 -w 800 -c 1000

--> Another example :

SERVICE ALERT: esx2;esx_net_receive;OK;SOFT;2;CHECK_VMWARE_API.PL OK - net receive=123.00 KBps

Corresponding command :

./check_vmware_api.pl -D $HOSTADDRESS$ -f auth.cfg -l vmfs -w 80% -c 90% -s BDD01 -o used

Is there some bug in monitoring plugins ?

Or the command doesn't works for notifications ?

Or it's due to Shinken ?

I must clarify that I receive another notifications from GLPI for another commands. Certains command send me notifications for some hosts and not for other. yet it is the exactly same command...

Does I missed something ?

Thanks for help.

GLPI 0.85.4 Monitoring 0.85.1 Shinken 2.4 Debian 7

[algorys]

It seems that SOFT alert doesn't triggers notifications, so is there a possibility to change that in a next version or not ?

Or is there a way to bypass that for certain commands ?

[claneys]

Hi,

SOFT alert doesn't trigger notification, it is a normal behavior. If you don't want use SOFT state, just set the max_check_attempts option on services or hosts to 1, then it will pass on HARD state immediately.

[algorys]

Ok,

But my hosts and services are defined by GLPI, so I will check that if it works with it. Thans for tip.

@claneys I've try to set like this in GLPI :

Maximum Number try : 1 Time beetween 2 controls : 5min Time beetween 2 try : 1

So I Have this alert (who's HARD) :

SERVICE ALERT: routeur;currentconnections;CRITICAL;HARD;1;SNMP CRITICAL - 1109

But there is not no NOTIFICATION after...

Does I have make an error ?

[claneys]

Do you still have the issue ?

[algorys]

Hello,

Sorry, to not update this issue. I've make a new install and it seems to work. I close this issue.

Thanks for help.

[claneys]

Glad to hear that.