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

Seems simple enough...but

I'm setting up an alert for a couple application monitors for Exchange. I want to alert whenever one of the components goes to a critical state. Seems easy enough..so I started with the # of Processes component and came up with this:

I set the threshold value to a number that I know is below it's current value...but the alert won't fire. I don't get it...anyone see what's wrong with this?

Thanks

Find more posts tagged with

Accepted answers

TohAtin

We use the exchange APM Monitor to watch all the processes then Advanced Alert manager configured an Alert named Application component Alert with trigger Conditions being Property to monitor APM: Component

Node Status is not equal to down

Trigger Alert when any of the following apply

Component Status is equal to critical

just make sure your thresholds are set and this will be a global alert

All comments

lchance

I typically just put it in this order:

Trigger Alert...all...

Component Name is equal to Number of Processes

Component Status is equal to Critical

I would not use the CONDITION GROUP for this. This order tends to work well for me. Good Luck!

TohAtin

Node Status is not equal to down

Trigger Alert when any of the following apply

Component Status is equal to critical

just make sure your thresholds are set and this will be a global alert

sgreath

Got it...thank you both very much.