Network Management

Troubleshooting Guide: Checking the alert history in the SolarWinds Platform

This troubleshooting guide shows how to check for the history of alerts directly in the database. It is helpful for troubleshooting scenarios such as when an alert was triggered but failed to send emails to its recipients.

First published date

5/31/2019 10:17 PM

Last published date

1/7/2025 11:06 PM

Overview

In any situation where you need to check the history of alerts triggered in the SolarWinds Platform for a specific object (nodes, interfaces, applications, etc.), the AlertHistoryView (View) in Database Manager is the best place to start. For example, you can determine when an alert was triggered and whether the alert action was successful. This article will teach you how to check for alert history in the SolarWinds Platform.

 

 

Product section

Orion Platform

Cause

-

Resolution

Collect the relevant information

Checking for alert history typically requires two things:

  • The name of the affected alert
  • The object that should trigger the alert (see How to obtain a node ID from the Web Console)
    Examples:
     - Nodes (http://localhost/Orion/NetPerfMon/No...spx?NetObject=N:172)
     - Interfaces (http://localhost/Orion/Interfaces/In...spx?NetObject=I:544)
     - Application Components (http://localhost/Orion/APM/MonitorDe...spx?NetObject=AM:2680)

NOTE: Both pieces of information are equally important because they will be used later as parameters for checking the history.
 

Check for validity of the alert-object relationship

Using the resource 'All Alerts this Object can trigger', you can verify if the alert is valid for the object to trigger. If this resource is missing, you can add it (with View Customization privileges) by following the instructions below.

  1. Navigate to the object details view.
    Examples:
     - Application Details - Summary
     - Node Details - Summary
     - Application Component Details
     
  2. Click the Pencil icon > ADD WIDGETS and look for 'All Alerts this Object can trigger' resource.
  3. Drag and drop it to the page and click DONE ADDING WIDGETS.

This resource should show alerts on the list. To validate the alert-object relationship, we can check for history.
 

Check the alert history

In your SolarWinds server, open the Database Manager and run the query below, replacing AlertName with the name of the alert and NetObject with the ID of the object:

-- Scripts are not supported under any SolarWinds support program or service.
-- Scripts are provided AS IS without warranty of any kind. SolarWinds further
-- disclaims all warranties including, without limitation, any implied warranties
-- of merchantability or of fitness for a particular purpose. The risk arising
-- out of the use or performance of the scripts and documentation stays with you.
-- In no event shall SolarWinds or anyone else involved in the creation,
-- production, or delivery of the scripts be liable for any damages whatsoever
-- (including, without limitation, damages for loss of business profits, business
-- interruption, loss of business information, or other pecuniary loss) arising
-- out of the use of or inability to use the scripts or documentation.

SELECT * FROM [dbo].[AlertHistoryView] WHERE Name = 'AlertName' AND EntityNetObjectId = 'NetObject' order by TimeStamp desc

Example: Using the alert name Alert me when a component goes down and the component object HTTP Bindings Monitor ID(AM:912), we can run the query and generate the results below which shows the TimeStamp and success/failure of actions configured in the alert.