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) > How to import OOTB alerts when an existing alert has the same name

How to import OOTB alerts when an existing alert has the same name

Updated: 2-10-2017

Overview

When importing out-of-the-box (OOTB) alerts, Orion alerting checks if an alert of the same name already exists. If you have already created an alert sharing a name with a new OOTB alert, it is not imported. This information details how to import the new OOTB alerts. To resolve, rename your user-defined alert in SAM and rerun the Configuration Wizard. The OOTB alert will import into SAM without issue.

Environment

  • Orion Alerting
  • SAM 6.4

 

Cause 

A user defined alert you created has a matching name to an OOTB alert SAM is trying to import during an upgrade. The matching names causes the new alert not to be imported.

 

Resolution

  1. In the Orion Web Console, click Alerts & Activity > Alerts, and click Manage Alerts.
  2. Select your alert and click Edit.
  3. Enter a new name for the alert and Submit to save.
  4. Rerun the Configuration Wizard. The alert imports after verifying the name is not already used and active.
 

 

Last modified
11:30, 13 Feb 2017

Tags

Classifications

Public