Watchdog 100P Traps/Alerting

So this does not appear to be an issue with the device, but your subject includes the word 'Traps', so I wanted to confirm if you have an issue receiving traps from the device and you wish to alert of those or if this is an alert definition issue.

When alerts do not fire, my go to is 3 things:

1. Review the SWQL code in the Trigger definition and execute it in SWQL Studio to see what is returned. This may well show up some logic issue
2. Simplify the logic in the alert if possible i.e. remove specific device filters and such
3. Make sure your Reset logic does not mean it immediately resets

I often find it is the logic structure where AND/OR statements are incorrect or the field/values not aligned to the conditions.

Are you able to share any screenshots of the values in the UnDP and the alert Trigger page.

I would really love to have a trap setup for the device, because that it how our other environmental devices are setup. 

See the attached screenshot for the Values for the UnDP, and the Alert Conditions. We are having a weird issue where we cannot see the action trigger page, but that is a whole other story. 

The node ip_address looks to be wrong it should be ‘starts with’ 192.168.