Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

High Packet Loss & Node Down

I was curious how many people have their High Packet Loss alert modified to not be triggered if the node status is equal to down?

I ask because I am thinking about doing this and was curious how it has worked out for anybody else that has done it. Currently when a node goes down I end up with both the High Packet Loss alert as well as the Node Down alert. I am trying to consolidate as much as possible so that for each problem type I only get one alert as to keep my techs from getting overwhelmed by alerts for only a few actual problems.

Thanks in advance for any input!

Find more posts tagged with

Accepted answers

All comments

mrxinu

Yeah, we see this a lot in the Top 10 page, too - the packet loss goes to 100% and that winds up taking up most of your view. Adding 'node status is not equal to down' on the High Packet Loss alert would squelch that noise. In the case of the Top 10 resource, an SQL filter of 'Status <> 2' cleans up the interface.

scottd

You could also use the Alert Suppression tab to say Supress if <node> is not up.

Just another way to write your alert if you wish...

byrona

Yeah, we see this a lot in the Top 10 page, too - the packet loss goes to 100% and that winds up taking up most of your view. Adding 'node status is not equal to down' on the High Packet Loss alert would squelch that noise. In the case of the Top 10 resource, an SQL filter of 'Status <> 2' cleans up the interface.

Thanks MrXinu, I will give it a try!

byrona

You could also use the Alert Suppression tab to say Supress if <node> is not up.
Just another way to write your alert if you wish...

Suppression actually won't work for something like this. When you use the suppression tab it is unaware of other logic associated with the alert. It will simply run the query against the entire database and if anything matches it will get suppressed.

To correctly suppress this it needs to be built into the trigger.

scottd

Your right, supression would work here only if you were just applying the condition to one node.