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

COMPONENT BASED ALERTS SEND MULTIPLE COMPONENT OBJECTS

Is it by design that a alert based on a Down component will generate multiple separate emails per down component?

For example, you have several Oracle table space component monitors.

Three of the 5 TS component monitors goes critical and you get 3 emails for each Critical component.

Whereas with an Application based alert you can set the Components with Problems macro. But you cannot use some of the the Component macros, so there are trade-offs.

I guess it makes sense to get a separate email for each component, but I'm wondering if anyone else has a way to deal with this situation.

Find more posts tagged with

Accepted answers

All comments

christopher.t.jones123

can you post a screenshot of the alert logic and message? I have a feeling that the reason it looks like you're getting three separate emails is because of the way that your message or logic may be configured.

hpstech

Thanks Chris - here is the Component trigger logic...

christopher.t.jones123

Hi hpstech,

thanks for that. Can you also show how the email message is configured? This looks functional, personally, I would move the component types up into the scope, and move the status down to the actual trigger condition. But its really a matter of 6 one way half a dozen the other

hpstech

Thanks again -