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

trigger action delay in advanced alerts

Regarding the trigger condition delay at the bottom of the advanced alert Trigger Condition tab: it defaults to 0. Has anyone noticed any problems with alert functionality if the value is left at 0? Should it be set to some positive value as a matter of practice? Just curious.

Find more posts tagged with

Accepted answers

All comments

FormerMember

zero means fire alert immediatly at time of trigger

any number here means delay for x amount of time.

FormerMember

any number here means delay for x amount of time.

Can you please elaborate on delay a little more? Let's say you have an alert configured for interface bandwidth > 90% and delay of 5 minutes. Does bandwidth have to be sustained for 5min > 90% for the trigger action to fire or will the action fire anyway no matter what the bandwidth is at the 5min mark?

freemen

Thanks for the reposnses, but what I was really asking is if anyone has seen any alert functionality problems arising from this value being set at zero.

Anyone?

FormerMember

Can you please elaborate on delay a little more? Let's say you have an alert configured for interface bandwidth > 90% and delay of 5 minutes. Does bandwidth have to be sustained for 5min > 90% for the trigger action to fire or will the action fire anyway no matter what the bandwidth is at the 5min mark?

Its the first one the bandwidth would have to ramain in the triggered alert status for 5 min and would then do the corresponding steps you have chosen for it to follow.

FormerMember

Thanks for the reposnses, but what I was really asking is if anyone has seen any alert functionality problems arising from this value being set at zero.
Anyone?

then I would have to say no issues on this part. I have a few where i actually want it to "confirm" there is a problem so I delay it but for most of my alerts they are set to zero and fire when found.

FormerMember

Can you please elaborate on delay a little more? Let's say you have an alert configured for interface bandwidth > 90% and delay of 5 minutes. Does bandwidth have to be sustained for 5min > 90% for the trigger action to fire or will the action fire anyway no matter what the bandwidth is at the 5min mark?

Its the first one the bandwidth would have to ramain in the triggered alert status for 5 min and would then do the corresponding steps you have chosen for it to follow.

Thanks HT. That's what I hoped would be true.

qle

Its the first one the bandwidth would have to ramain in the triggered alert status for 5 min and would then do the corresponding steps you have chosen for it to follow.

I've read that once the condition trigger is met, it will check again at the delayed interval before actually triggering. In other words, using the aforementioned example, Orion doesn't check that the bandwidth is above 90% during the entire five minute delay. Instead, once it sees it's above 90%, it'll wait five minutes and then poll again and only if the results of the second poll are above 90% will it trigger. Someone, please correct me if I'm wrong.