Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Orion Platform > Orion Documentation > Orion Platform Administrator Guide > Use alerts to monitor your environment > Changes in the alerting engine

Changes in the alerting engine

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

Views: 549 Votes: 0 Revisions: 5

This topic applies to all Orion Platform products except for the following products:


As of Orion Platform version 2015.1, alerts are no longer created with the desktop-based, Advanced Alerts Manager or Basic Alerts Manager. Alerts are instead created and managed in the SolarWinds Orion Web Console.

The Alerting Engine Service has been removed and you will no longer see this service under the Orion Service Manager or Windows Services.


Alerts that you created in the desktop-based Alert Manager are migrated to the web-based alerting engine when upgrading to Core version 2015.1 or later. Some alerts may not be successfully migrated and include information about why they were not migrated in the migration log. You can view the alert migration logs in the informational banners displayed after you update your installation.

Changed or removed functionality

The suppression section has not been carried over to web-based alerting. Use options, such as Condition must exist for more than, in the trigger conditions to accomplish similar tasks.

Database changes

The following are a list of tables that have been changed that you may be using in custom SQL queries:

  • Engines has been renamed to AllEngines
  • Nodes has been split into NodesCustomProperties, NodesData, and NodesStatistics
  • History has been split into table-specific history tables, such as the AlertHistory table.

The new alerting engine also includes the following new alerting tables:

  • Actions
  • ActionsAssignments
  • ActionsProperties
  • AlertActive
  • AlertActiveObjects
  • AlertConditionState
  • AlertConfigurations
  • AlertHistory
  • AlertHistoryView (introduced in 2015.1.3)
  • AlertMigrationLog
  • AlertObjects
  • AlertSchedules

Macro or variable changes

The following variables are no longer valid:

  • ${Property}- The property the alert is monitoring. You can select a new variable with the specific property you want to view.
  • ${TriggeredValue} - The value that triggered the alert. You can select a new variable with the specific property you want to view.
  • ${AlertStartTime} - When the alert active. You can use the Time of Day scheduler to control when the alert is active.
  • ${AlertEndTime} - When the alert is no longer active. You can use the Time of Day scheduler to control when the alert is not active.
  • ${ObjectSubType} - Determines if the node supports SNMP or is ICMP-only. You can use Node.ObjectSubType as the macro name.
Last modified