Nagios Support Forum

I needed to be configured before it can know how to send the notifications so make sure the unconfigured objects are configured.

Here is one thing you may be interested in, there is an option called Volatile that when enabled, it will send the Notifications for multiple criticals in a row which is what you are looking for.
To enable it, go to the Core Config Manager > Services menu and edit the service in question. Go to the Check Settings TAB and on the bottom is the Is Volatile option. Set it to on and save the change.
https://assets.nagios.com/downloads/nag ... vices.html

This will allow 2 Criticals in a row to sent notifications.

Thank you for that I will enable it but why is it that the OK state with 9 lines is still showing up as critical?

What it looks like is that the string of data in the 6th field is getting evaluated which is larger than 2 so it matches.
Because the device is using different variables for the traps, you are going to have create custom traps for all of them.
You will have to add another match and figure out what type of data to match on and add it to that trap definition to it does not happen again.

There has got to be a better way.

To tell you the truth, it is an issue with the device.
It sends the traps in different order, removes data from certain values depending on the data it is sending.
I have never seen another device do that so if you want to get consistent data for that trap, talk to the manufacturer to see if they will fix it.

Is it possible to match the ID like this

MATCH enterprises.4184.2.5.2.0: > 2

instead of $6 for the 6th line?

The following link has what you can use for the MATCH option.
http://snmptt.sourceforge.net/docs/snmp ... CONF-MATCH

The $x is any variable (example: $3, $A etc).

It looks like it supports other variables instead of the index number.
If you scroll up in the web link, to the FORMAT section, you should be able to use the variables in that list.
http://snmptt.sourceforge.net/docs/snmp ... ONF-FORMAT

You are trying to match an OID and it's variable greater than 2 at the same time and it looks like that will not work.

Using these variables may work Then try setting the Match Mode to or.

Create the Match statements like this.
That may make the match check for 3, 0r 4, or 5, or 6 and trigger the trap.

But this is something you will have to test.