So, without seeing the values being returned by your pollers, I am looking specifically at the alert logic right now.
This is a replica of your situation, just using a different tabular poller:
Now, when we look at the raw SQL syntax behind this alert, we can test and get the following error:
Basically, what we are seeing here is a problem on line 12. The 'UniqueID' field is stored as a varchar data type in the CustomPollerStatusTable view that we are referencing, so we cannot use mathematical operations here. (You cannot have a mix of letters and numbers greater than an integer, in this case 0).
To verify, we can comment out this portion of the query, and we get the following results:
To verify if this is the same issue you are experiencing, in the Advanced Alert Manager, you can define your alert, then change the type of property to 'Custom SQL Alert' for 'Custom Node Table Poller' and click the "Verify SQL" button:
If you see the same type of error as this, then try and comment out the last section as below (notice that I moved the 'AND' down a line to ensure that it was commented out as well):
If this works, as seen above, then your final alert will need to be a Custom SQL Alert like this and this should be the syntax you use:
WHERE ( (Nodes.Caption = '<INSERT NODE NAME HERE>') AND (CustomPollers.UniqueName = 'cikeTunRemoteValue') AND ( NOT (CustomPollerStatusTable."Value" = '<INSERT PEER IP HERE>') ) )
If this is indeed the case, I would open a ticket with SolarWinds as this might be a bug in the software. Hopefully this is not seen in NPM 11.5 with the new web engine for alerts. I don't currently have a RC installed to test the theory on unfortunately.
Maybe aLTeReGo or rob.hock can get some visibility on this internally?
Good luck! Please let us know what you find out!
Loop1 Systems: SolarWinds Training and Professional Services
- LinkedIN: Loop1 Systems
- Facebook: Loop1 Systems
- Twitter: @Loop1Systems