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

Advanced Alert question

What is the purpose of the option on the Trigger Condition tab that allows you to set a time delay on the alert? How is that different from the time delay that can be placed on an alert action on the Escalation tab?

When would you use one or the other? Should you use only one at a time, or can they be used on the same alert?

Thank you.

Find more posts tagged with

Accepted answers

mcbridea

Patriot,

The "Check the alert every" option sets the db scan frequency. The "do not trigger until..." option lets you set how long the alert condition has to be true for Orion to trigger. Setting the Do not trigger" option to a more frequent setting than the "Check for alert" frequency doesn'tmake sense. You can set the polling interval for the critical nodes to 1 minute to make sure the db data is fresh but be careful not to do this across all elements or you will overload your pollers.

All comments

byrona

You can use the Trigger Condition time delay in conjunction with the alert checking frequency to basically control how many checks in a row it has to meet the trigger conditions to be true. Of course when you do this you also need to take your polling frequency into consideration to make sure the alert isn't checking the same value twice.

A use case for this would be checking a slow website; because the website is slow I want Orion to see the Trigger Condition in a failed state twice before it triggers an alert.

The Escalation Tab is for a completely different function. This is for escalating alerts to yet another notification destination in the event the alert is not getting resolved. As an example; you can have an initial alert fire off to your NOC, you can then use the delay on a second action so that it fires off to a manager an hour later if the alert is not resolved.

Hope this helps!

freemen

Thanks, byrona.

patriot

Byrona,

What is the difference then between the alert evaluation frequency on the General tab and the "do not trigger this action until...." setting on the Trigger Condition tab? I thought that the setting on the General tab controls how often Orion polls the DB looking for that alert trigger.

No?

mcbridea

Patriot,