Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

Home > Success Center > Server & Application Monitor (SAM) > Component status vs component availability alerting

Component status vs component availability alerting

Table of contents

Updated April 19, 2017

Overview

This article describes the difference between selecting to alert on component status or component availability. 

Environment

All SAM versions

Detail

These are two different tables used to trigger the alert which depends on the alert condition selected (status or availability):

Status SWQL
SELECT E0.[Uri], E0.[DisplayName]
FROM Orion.APM.Component AS E0 
WHERE ( ( E0.[Status] = '2' ) OR ( E0.[Status] = '14' ) )


Availability SWQL
SELECT E0.[Uri], E0.[DisplayName]
FROM Orion.APM.Component AS E0 
WHERE ( ( E0.[ComponentAlert].[ComponentAvailability] = 'Critical' ) OR ( E0.[ComponentAlert].[ComponentAvailability] = 'Down' ) )

 

Due to the AppInsight application monitor architecture, some components within AppInsight such as, All databases (AppInsight for SQL) and All sites (AppInsight for IIS) are not included in the Orion.APM.Component status SWQL because a component may contain multiple databases, multiple sites, or site bindings. The SWQL which uses the Component.Alert availability will then trigger for such objects.

SolarWinds recommends using the Component.Alert availability to avoid missing any alerting issues. 

 

 

Last modified
19:50, 18 Apr 2017

Tags

Classifications

Public