Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

Home > Success Center > Server & Application Monitor (SAM) > Create an alert for monitored components in SAM

Create an alert for monitored components in SAM

Updated: 3-30-2017

Overview

This article provides steps on how to implement an alert for components in your environment. Components include monitored applications in SAM, only available with SAM in your Orion environment. When monitored, you add applications as nodes monitored with templates and component monitors.

Environment

  • SAM 6.2.0 and later

Steps

These steps include options and information for different versions of SAM. SAM 6.2.4 introduced a new interface for accessing options.

In SAM 6.3 and later

  1. In the Orion Web Console, click Alerts & Activities > Alerts, and click Manage Alerts.
  2. Click Add New Alert.
  3. On the Properties tab, enter a name, description, set the trigger checking frequency, and set the severity. The severity helps group the triggered alerts. And click Next.
  4. On the Trigger tab, create the triggers for the alert. For the I want to Alert on drop-down menu, select Component.
  5. Select the Scope of the alert to trigger against all objects or specific objects in your environment.
  6. For the trigger conditions, select if all or one of the conditions must be met to trigger from the drop-down menu.
  7. For the trigger, Component is selected by default. You can then select a field (property) or an event for the "component", a comparison (equals, greater than, etc), and a value. For fields and events, you can select one to open a window for searching and selecting one for comparison.
  8. Select a component type and a metric from the list. You can add multiple triggers to the alert, to trigger one or all for the alert and and amount of time for the trigger to run (optional).
    For example, you could set up an alert that triggers for the Adobe Acrobat Update Service :
    • Set the Scope as "Only following set of objects" with these settings: Component "is equal to" with a value of Adobe Acrobat Update Service (which is a monitored component in SAM)
    • Trigger set as: Component > Status > "is not equal to" > Up
    • Trigger set as: Node > Status > "is not equal to" > Down
  9. When done, click Next.
  10. On the Reset Condition, set conditions for resetting the alert. For example, you could select to reset when no longer true. When the time runs again for the alert, if the condition triggers are not longer met, the alert resets. You could also set it to be manually reset to require interaction. And click Next.
  11. For the Time of Day tab, set the schedule for the alert running. This can be always on or only run on specific days and times. For example, alerts to trigger for component resource usage could trigger just for peak times everyday or always.
  12. For the Trigger Action, set actions to take when the alert triggered. You can send emails, send SMS messages, change custom properties, manage resources, and more. Click Add Action, select and action, and complete the settings and information for the action. You can add multiple actions.
    For example: To send an E-Mail, click Add Acton, and select Send an Email/Page. Here, you can fill in pertinent information, such as to address for this E-mail to get sent to, SMPT server selection, etc. To introduce dynamic variables to your E-Mail messages, perform the following within the Message tab of the E-Mail configuration:
    1. Component Name
    2. Caption
    3. Status or Error
    4. Click Insert Variable on the right hand side of the message body.
    5. Search and add the following variables (checking the box to the left of the variable adds it to the builder):
      Modify that message block to have these variables be in readable format.
    6. Copy that same message block that you created above (content within the red box). Finish any configuration for this particular E-Mail action.
  13. For the Reset Action tab, enter actions to complete when resetting the alert. These actions complete based on the Reset Conditions. This step ensures that these events are tracked as Events within Orion, which provides easier auditing and quick high level views of application availability.
  14. On the Summary page, you can get a real time test to see how many objects this alert will trigger on. This is helpful for fine tuning the alert and ensuring that it will capture what you are looking for without applying the alert to your environment.
  15. Submit when complete. The alert is added to SAM and runs according to the settings. You can edit and manage the alert anytime through the Manage Alerts page.

 

In SAM 6.2 through 6.2.3

  1. In the Orion Web Console, click Settings > Manage Alerts.
  2. Click the green + button to add a new alert.
  3. Fill in the first Properties tab with pertinent details related to this alert.
  4. On the second Trigger Condition tab, set the first dropdown to I want to Alert on a Component.
  5. Then, set a scope to the particular Component or Application Name (Screenshot targeting a component below). This last step is only optional. 
  6. Include a filter to the trigger condition to ensure you don't receive alerts on this component if the node hosting is down. The filter could be something like shown in the screenshot below where  the node status is not equal to down.
  7. In this scenario, set up an alert that triggers only when the Adobe Acrobat Update Service (monitored component), has a status not equal to Up and the node hosting this component has a status not equal to Down.
  8. Leave the the Reset Condition tab as default. 
  9. Set the Time of Day tab based on your preference.
  10. The Trigger Actions tab is where you can configure what actions are taken once this alert has been triggered.
    To send an E-Mail, click Add Acton, and select Send an Email/Page. Here, you can fill in pertinent information, such as to address for this E-mail to get sent to, SMPT server selection, etc. To introduce dynamic variables to your E-Mail messages, perform the following within the Message tab of the E-Mail configuration:
    1. Component Name
    2. Caption
    3. Status or Error
    4. Click Insert Variable on the right hand side of the message body.
    5. Search and add the following variables (checking the box to the left of the variable adds it to the builder):
    6. Modify that message block to have these variables be in readable format.
    7. Copy that same message block that you created above (content within the red box). Finish any configuration for this particular E-Mail action.
  11. Another example: Click Add Action, and add Log the Alert to the NetPerfMon Event Log.
  12. The Reset Action tab can contain the same information as above, but keep in mind not to hard code any values so you don't get a "NODE DOWN" email when the node actually went back online. Paste the message that was copied earlier from the message above into the message of this action. This step ensures that these events are tracked as Events within Orion, which provides easier auditing and quick high level views of app availability, etc.
  13. On the summary page, you can get a real time test to see how many objects this alert will trigger on. This is helpful for fine tuning the alert and ensuring that it will capture what you are looking for without applying the alert to your environment.

 

Last modified

Tags

Classifications

Public