Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Server & Application Monitor (SAM) > SAM 6.5 Administrator Guide > Create and manage alerts for SAM > Alert migration to the web for SAM

Alert migration to the web for SAM

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

Tags

Classifications

Public