I've created an advanced alert to notify me when a node goes down based on the following:
Status is equal to Down
Vendor is equal to Windows
However this doesn't seem to work as I'm not getting alerts when the Windows systems go down. I've used the test feature in the alerts area and successfully received the notifications from this. I've also ensured that the alert is enabled. Is there something obvious that I'm missing?
Yes, I'm sorry- typo on my part. ""Node Status" is configured in the query (I don't believe there is a "Status" only option).
Perhaps some other obvious item I'm missing? Is anyone else successfully using "Vendor" in their Alert condition?
Thanks again for the support.
Well, Orion is still set at the default 4 minute interval for the page to refresh. But I manually kept refreshing after disabling the interface and, at about 120 seconds, it went to warning, and then another 60-120 seconds, it changed to 'Down' status and I received an alert (email). within seconds. So, it seems that NPM is the slowest link- I have changed the poll interval for NPM down from 120 seconds to 60. Is there some setting that sets the node in 'Down' state immediately after 60 seconds instead of 'Warning' (as seen in Orion)? (Though I think the 'Warning' is related to packet loss...)
I manually kept refreshing after disabling the interface and, at about 120 seconds, it went to warning, and then another 60-120 seconds, it changed to 'Down' status and I received an alert (email).
You got the first part, changing the status polling interval to 60 seconds. The second part of what your looking for is under 'Advanced Settings' in System Manager. Go to the 'Node Warning Interval' tab. From there you can drop the amount of time that a node will sit in the warning state before going to the down state.
Orion pings each node every [Node Polling Interval - default 120 seconds]. If no response is received, the node status switches to Warning and we start polling it every 10 seconds. This continues until either we get a response - node status switches back to Up and we resume normal polling - or the "node warning interval" (default 120 seconds) expires and we mark the node Down.
You can configure the node polling interval on a per-node basis and you can set the default node polling interval for new nodes in System Manager under File > NetPerfMon Settings > Polling. You can change the node warning interval in System Manager under File > Advanced NetPerfMon Settings.
I'm anxious to hear what kind of response you get back from either the Thwack community or Solarwinds themselves. I'd like to do something similar with my alerts, but before I go and break something that's currently working I would like to know if this is suppose to work. Honestly I don't see any reason why it shouldn't, but then again I just use the code, I don't write it. 🙂
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.