Submit a ticketCall us

WebinarVisual Monitoring Tactics: Getting More Log Search Value from SolarWinds Log & Event Manager with nDepth Webcast

Do things seem to make more sense when they are visualized? Are you an IT professional or security expert with a wish for more cybersecurity tools that provide an intuitive visual experience? Join Alexis Horn and Jamie Hynds from SolarWinds as they demonstrate how the nDepth feature in LEM can help make visualizing log search results a reality.

Register now.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Troubleshooting Guide: Checking the alert history in the Orion Platform

Troubleshooting Guide: Checking the alert history in the Orion Platform

Updated November 27, 2018

Overview

In any situation where you need to check the history of alerts triggered in Orion 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 Orion Platform.

 

00217176_1.PNG

Environment

  • Orion Platform

Steps

Collect the relevant information

Checking for alert history typically requires two things:

 

  • The name of the affected alert
    clipboard_e4ef3961f607f3a1aab84af073e995759.png
     
  • The object the alert should trigger (NetObjectID)
    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 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.
    clipboard_eebdf287a701f6200cc1f3d62221c1e40.png
     
  3. Drag-drop it to the page and click DONE ADDING WIDGETS.
    clipboard_ee0958b946a7559dd6b4986b2672128dc.png


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 Orion 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:

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.

 

00217176_2.PNG

 

Last modified

Tags

Classifications

Public