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 > Network Performance Monitor (NPM) > Purposes of acknowledging alerts in Orion

Purposes of acknowledging alerts in Orion

Table of contents
Created by Eric Bryant, last modified by Erica Gill on Jul 08, 2016

Views: 1,820 Votes: 2 Revisions: 9

Overview

This article explains the benefits of acknowledging alerts in the SolarWinds Orion Web Alerting engine. 

Environment

All Orion Core versions

Detail

Main points of the functionality of Acknowledgment of alerts in Orion

  • Intended feature of Acknowledgement of alerts is meant for physical intervention from a user.
  • Auto Acknowledge of alerts is not possible without outside third party unsupported user configuration (workarounds are possible).
  • Acknowledge function gives user a audit trail of physical intervention.

 

When an alert has triggered and becomes active, you can then acknowledge it. After an alert is acknowledged, alert actions in higher escalation levels are halted and the time it was acknowledged and the account that acknowledged it is recorded. You can also add notes that other users can read.

 

Depending on your organization, acknowledging an alert can have different purposes outside of halting further notifications. The most common purposes are to provide an audit trail or to prevent multiple people from working on the same issue. Auto Acknowledgement would not be a recommended procedure in most environments as it can be ambiguous if a problem has been addressed in the monitoring system in particular. 

 

For more information, see to the following:

 

 

Last modified
01:54, 8 Jul 2016

Tags

Classifications

Public