Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Orion Platform > Orion Documentation > Orion Platform Administrator Guide > Use alerts to monitor your environment > Alert migration to the web

Alert migration to the web

Created by Caroline Juszczak, last modified by Magdalena.Markova on Dec 21, 2016

Views: 18 Votes: 1 Revisions: 5

The Advanced Alert Manager and the Basic Alert Manager are deprecated in SolarWinds Orion Core 2015.1 and later. A web-based alerting engine replaces the previous alerting engine and includes new alerting variables. See General alert variables for more information.

To facilitate using the web-based alerting engine, part of the upgrade process migrates alerts created with the desktop-based alerting engine to the web-based alerting engine. All alerts are migrated, including alerts that are disabled.

Migration issues

Some alerts may not be successfully migrated. The migration log records all alerts that are migrated and includes error messages for alerts that either cannot be migrated or that are not migrated successfully.

Common reasons that migration may not be successful include:

  • Invalid alert variables or macros - Some variables are no longer supported.
  • Invalid conditions - Some conditions are no longer supported.
  • Large alert scope - The number of objects that are relevant to an alert may be too large to migrate.

Limitations to migrated alerts

Once an alert has been migrated, you can only view the alert definition through the web-based Alert Manager. You can no longer click on the alert in the views.

 
Last modified
07:26, 21 Dec 2016

Tags

Classifications

Public