chriso

We primarily use the suite of Solarwinds products along with Kiwi for syslog messages. Also, we use Scom, Infoblox, and are looking at tealeaf through IBM just to name a few of the bigger ones.

Solarwinds NPM SAM VNQM WPM Engineers Toolset Kiwi Splunk Compuware Agentless Gomez SCOM Savvius Wireshark Gigamon Network Instruments

BGP, EIGRP, OSPF, etc... peer changes is usally a good one to alert on as well that could trigger a syslog message or ticket to be sent ot the correct group.

I agree with Scott Dawson, do not upgrade if you have many custom alerts. We have over 1500 alerts, and a decent amount are custom. We backed out when we saw this issue. I am not sure why they would make a change like this all of a sudden.

I found out what I can do. A hub and spoke topolgy will not work in this case as these are single connections from one site to a IPSLA test router that measures VoIP jitter, just on a large scale. What I ended up doing was going to custom option, slecting all nodes (including the IPSLA router) and then pointing each site…

Why would this have been a decided change with NPM and SAM? We just had to back out our upgrades due to this to the previous version because many of the alerts were not identifying the correct variables. We have over 1500 alerts, and custom reports setup and going through each of them one by one is going to be extremely…

There is no trigger condition, your query as it stands now it merely polling NodeID, and Caption from the Nodes table. This would work more for a generic report query than an alert. What are you trying to alert on? I may be able to point you in the right direction if I knew what the alert was suppose to trigger on. You may…