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

Alert logic if a service is not running on either or 2 servers.

I have a case where a critical service would normally be running on either of 2 peered servers. So it is only ever running on 1 server. I am trying to create an alert if it is not running on either. My alert logic is below, however in testing it is not triggering. Thoughts?

Find more posts tagged with

Accepted answers

brscott

NOTE: I just made this up, so there is a high chance of error here. Also note this is just one of several ways to do this.

The logic here is that

1) setup the alert so that it would normally alert on EITHER process being down.

2) enable complex conditions, and set the "alert can be triggered if [more or equal] [2] objects (at the same time) have met the specified condition"

All comments

brscott

NOTE: I just made this up, so there is a high chance of error here. Also note this is just one of several ways to do this.

The logic here is that

1) setup the alert so that it would normally alert on EITHER process being down.

2) enable complex conditions, and set the "alert can be triggered if [more or equal] [2] objects (at the same time) have met the specified condition"

jcm

Thanks for the feedback and the tip. I actually want to alert if the service is not running on both servers, it should be running on one or the other. I think adding a complex condition is a good way to go.

Thanks again and will test tomorrow.

jcm

Thanks, I made it work on a test system this morning. I ended up making a template for the process for each server and configured the trigger as a complex condition. I did not test against application ID's in that case.