gdsw

Thanks for your help and time with this, and for the tips throughout!

Thanks Adam, So it was just a case of adding the SolarWinds Node Variable (${N=SwisEntity;M=Node.NodeID}) to the end of the SQL statement? Really good to know, thank you for this! I've tweaked the code a little and simulated the alert with a secondary device of a HA pair (as its VPN would have a different status): VPN1:…

Thanks for your reply here. I think I've missed some vital info (the trigger detail) based on your latest response. For the trigger Condition, I am using 'Custom Node Poller' drop-down item, the statement is similar to your suggestion (I believe). The SWQL statement is pulling from…

Thanks Adam, And you're absolutely right, I did mean NodeID, sorry for any confusion. I have the SWQL in place allowing the status of each Network devices' VPN status to be represented; SELECT SWN.nodeName As [Node], NodeID, CPN.AssignmentName, CPN.Status As [Overlay&Serial], RowID, DateTime As [LastPoll] FROM orion.Nodes…

We found the 'routing_key' had to be statically set when troubleshooting a similar issue with group down alerts into Pagerduty previously.

Hi Marc, Many thanks for taking the time to have a look here. Seems there is mass duplication one the results for some reason (around 60 odd lines for a single site/ device), I guess each of the joins are duplicating the data? I added the CustomPollerID field to see if could get a better idea of what's going on, seems…

Thanks for both of your replies, I'm still working on this so hopefully I'll be able to share this if I ever get it working as required.