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

Application component goes down outside an alert window doesn't trigger alert when the window opens

Hi all, I'm trying to figure out if this is normal behavior or not...

I have alerts set up to send emails if an application component goes down. I have time of day qualifiers on the alert actions (not the alert itself). I have several different actions so it can alert first shift, second shift, etc. I do not have anything set to go overnight. If something goes down overnight, when the first shift comes in, and the time window for the alert opens, should they get alerts for everything that went down over night if it is still down? Does not having an action set up for that time window mean that nothing will happen?

Thanks,

Mark

Find more posts tagged with

Accepted answers

All comments

aLTeReGo

Correct, this is functioning as designed. If at the time when the error occurs there is no defined action to take, then no action is performed. Having an action defined that allows for these alerts to be sent in the future does not mean they remain queued up until that time. The only way this would work in your scenario is if you defined the alert as reoccurring. E.G. continue to send me an alert once every [minute/hour/etc] until the issues is acknowledged or resolved.