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

I have dependencies set up, but child email alerts are still coming through

So I have several dependencies set up for field sites where it's:

Parent (Main Site Router)

Child:

- Site group containing a server, switch etc

In the event of high packet loss or high latency, shouldn't I only be getting the email alert if the main router is suffering from the problem?

Find more posts tagged with

Accepted answers

All comments

lbrowne

So I found out that the alert suppression is a different function, and that it can be a pain to set up.

All I want is if the parent router(s) is having either packet loss, high latency, or is down, I don't get an alert for every node at the site...

RichardLetts

No. Unfortunately dependancy only affects the Node-Down type alerts, and not the others.

i.e. if the parent node is down it puts the dependent notes into 'unknown' rather than 'down' state.

this doesn't affect 'up but not working quite properly' type of alarms. For that you have to code them yourself in the filters, which is nigh on impossible,

for the alerting folks this would be a rule of the form:

'AND this alert is not also triggered (or about to be) on a node that is a parent dependency of the current node'

which might be worth creating an idea for...

lbrowne

Thanks a bunch for the reply

It really seems like with Dependencies, they stopped without finishing. Dependencies are quick and easy to create, you should be able to select alert suppression through building dependencies instead of just up/down notifications.