nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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
Store

Suppress High Packet Loss

FormerMember

I modified the High Packet Loss Monitoring alert a couple of days ago:

Under Trigger Condition I added "Node Status is not equal to Down".

When I made the change it ran cleared the High Packet Loss alerts and just left the Node is down alerts.

Yesterday a node went down "is still down" and the Trigger condition does not seem to work as I have both "High Packet Loss" and "Node is down" for this alert.

Any ideas as to why or how to correct/

Thanks,

Find more posts tagged with

Accepted answers

FormerMember

Would that not effectively just disable the alert from triggering? - i.e. we have packet loss so mark node warning, but don't trigger the alert because it is warning.

I want to see the alert originally trigger to tell me theres a response issue since the node isn't necessarily down. However, if it is determined that the node is down, don't alert anymore.

Maybe I need to modify the reset condition as well.

*** Update ***

Updated Reset condition to be:

Reset when Any is true

precent of loss is less then 5%

node is equal to down

*****

seems to work via my quick test.

All comments

mcbridea

Before a node goes to down status it goes into warning status. This will cause the packet loss to trigger. Add "Node Status is not equal to Warning" and you should be OK.

FormerMember

Would that not effectively just disable the alert from triggering? - i.e. we have packet loss so mark node warning, but don't trigger the alert because it is warning.

I want to see the alert originally trigger to tell me theres a response issue since the node isn't necessarily down. However, if it is determined that the node is down, don't alert anymore.

Maybe I need to modify the reset condition as well.

*** Update ***

Updated Reset condition to be:

Reset when Any is true

precent of loss is less then 5%

node is equal to down

*****

seems to work via my quick test.

networkingkool

Hi to reply to this old post.

Today I also get into this thing. I do many things but cannot suppress High Packet Loss Monitoring. Then I think about the logic of Alert Suppression and Trigger Condition. The Suppression Condition should happen before the Trigger Condition in order to suppress that alert itself. Therefore I will set 3 mins delay to Trigger Condition and set Alert suppression to Node Status equal to Down. It works very well.

Your way work well with the first purpose, but the reset condition doesn't make sense. I get Event message like this "Node XXXX's packet loss has dropped from above 40% to below 5% and is currently 100 %."

Lol. The reset action should be negative to trigger action.

stuartwhyte

I've found that I get packet loss alerts when the device has been down and has come back up as the packet loss changes through 80%, 60%, 40% etc and the only way to suppress is to put a longer "hold" time on the alert, which inst exactly ideal. Still looking for the best solution