Documentation forServer & Application Monitor

How alerts work in SAM

An alert is notification that there is a problem with a monitored element. Orion comes with hundreds of predefined alerts for common problems such as a node or application going down, SSL certificate expiration, website failures, and many other problems.

Many predefined alerts are enabled by default, so you are alerted about issues as soon as you use Discovery to find servers and applications in your environment and add them to the Orion database. Here are some examples of how SAM utilizes the alerting feature in the Orion Platform:

  • Alerting on an application: SAM provides many preconfigured alerts that notify you if the status of an application changes (for example: Up, Down, or Unknown) based on whether a component monitor reached a warning or critical threshold. One alert can notify you about a warning, critical, down, or unknown state for the application.
  • Alerting on a component: If you create an alert for each component monitor in a SAM application monitor template, you will receive one alert for each component that exceeds a threshold. Alerting on a component monitor can be beneficial if you have custom scripts where you must be notified if the output of the script crosses a specific threshold.

    Monitored objects, such as nodes and applications, must exist in the Orion database before creating or configuring alerts.

SolarWinds recommends that you identify who will receive warning or critical alerts.

By default, alerts appear in the Active Alerts widget on the Orion Home page.

To see all alerts, click the All Active Alerts button in the Active Alerts widget, or click Alerts & Activity > Alerts. When the All Active Alerts page appears, you can:

  • Acknowledge an alert that you are working on
  • Click any alert to open the Alert Details page for more information
  • Click Manage Alerts to enable/disable, add or edit any alert.

You can create your own alerts, either by duplicating and editing a predefined alert, or by creating a custom alert. Alerting is very powerful and can be complex, with multiple trigger conditions, reset conditions, and actions.

To learn more about alerts, see:

Did you know that when SAM alerts you about an application failure, you can use SolarWinds IPAM to quickly determine if a broken or missing DNS record is at fault? You can then use SAM to troubleshoot the service further.