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

Suppressing or rolling up alerts when many nodes are down

esamurai

Hi, I have NPM running and there can be situations where 113 nodes become unreachable at the same time. I was wondering if there was a limiter, or way to ask the Alert manager to stop sending alerts if the Alert-per-minute rate exceeds some value. Today, when there were 113 'node up' alerts, I noticed that the email daemon at the pager company actually supressed many of the sent emails & returned "Undeliverable" messages.

I guess that I could try using some central router "A" as a: "if router A down, then don't alert on any switch" logic, but I was wondering if one of you has cooked up some kind of alert limiter?

Right now i many monitor switches and routers, in a star topology, mainly. On my other NPM box, there are a wide variety of devices, and the topology is not as simple. A rate-limiter type of function could help me from jamming a modem or causing the pager company to treat me like spam.

Find more posts tagged with

Accepted answers

mcbridea

I have not seen a limiter but you can suppress multiple devices. Check out this post

All comments

mcbridea

I have not seen a limiter but you can suppress multiple devices. Check out this post

mrxinu

I understand the problem, but I'm having a hard time coming up with a solution (even a really wild one). Let me ask you this, though. Why are 113 of your nodes going down at once? Are they often-failing nodes? If you have a big batch of fragile nodes, maybe it may make sense to create a custom property to identify them, exclude them from your general 'Node Down' alert, and then handle those separately (i.e., not emailing about them).

FormerMember

You idea about a supression rule is your best bet provided your "fragile" systems are all behind at least one common device, i.e Router or Switch. Looking to see if an upstream device is very effective.

The supression of alert would be to alert on only that device and mark the devices underneath it as unreachable rather then DOWN assuming that is your alert is based on Node down.

mrxinu

You idea about a supression rule is your best bet provided your "fragile" systems are all behind at least one common device, i.e Router or Switch. Looking to see if an upstream device is very effective.

Agreed. If he has a single point of failure that would be great.