Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > A configured alert is not triggered

A configured alert is not triggered

Created by Aileen de Lara_ret, last modified by MindTouch on Jun 23, 2016

Views: 3,929 Votes: 1 Revisions: 2


This article provides brief information and steps to resolve the issue when configured alerts do not trigger, or send emails.



All SAM versions


The properties for the configured alert are incorrect.



Do the following steps to check if the alert is properly configured:
1. Log in to the Orion server and start the Advanced Alert Manager.
2. Select the alert in question and click Edit.
3. Under the General tab, the Enable this Alert should be ticked.
4. Under the Trigger Condition tab, the correct property to monitor is selected.
    For SAM applications, select APM: Component or APM: Application.
5. For Custom Poller alerts and the poller is returning a table, Custom Node Table Poller should be selected.
6. Check that the correct condition are used in the Condition Groups:
    ALL: All conditions are true in order for the alert to trigger.
    ANY: The alert will trigger if at least one of the conditions is true.
    NONE: The alert will trigger if at least one of the conditions is not true.
    NOT ALL: The alert will trigger if none of the conditions is true.
7. Under the Reset Condition tab, check that the Reset when trigger conditions are no longer true is used.
    This option is used in most cases.
8. Under the Alert Suppression tab, check that no suppressions are defined.
    If a node or an object is to be excluded, this should be done under the Trigger Condition tab.
9. Under the Time of Day tab, check that the alert is configured to trigger any time.
10. Under the Trigger Actions tab, check that at least one Send E-Mail/Page action is added.
11. Check if the correct and valid e-mail address or addresses are provided in the To, Cc, and Bcc fields.
12. Verify the SMTP server settings.


If there are still issues with the alert, check the AlertLog table in the database. This contains information regarding each alert trigger or reset.
1. Go to Start > SolarWinds Orion > Advanced Features > Database Manager.
2. Click on Add default server.
3. Right-click on SolarWindsOrion database and select New query.
4. To display any e-mail errors, paste the following query and click Execute.
    SELECT * FROM AlertLog
  WHERE ActionType = 'EMail'
  AND Message  LIKE '&Fail%'

Check the Message column in the results. This contains the error/s in detail.
You can right-click on a cell with the error, select Copy data and paste the error in Notepad.
If there are any SMTP server errors, this message will help determine the cause of the error.




Last modified