The RUM Console is able to manage alert definitions on different versions of the Central Analysis Server (CAS) and to determine which alert definitions can be published on each report server.
The Alert management screen lists alert definitions coming from all CAS instances. However, definitions coming from one server may not be available for publishing on other servers, depending on the server version, alert type, metrics, and parameters supported by each of these devices. In general, alert definitions compatible with older CAS versions are available for publication on the latest CAS version, but alert definitions compatible with the latest CAS version may not be available for publication on older CAS versions.
When defining a new alert:
You can only assign a new definition to a CAS that supports the selected alert type . This is automatically ensured by the RUM Console, so you will not be allowed to assign an alert to a report server that does not support a particular type.
You can only choose from a common set of metrics supported by every CAS selected for publishing in the alert definition. This set is defined and displayed automatically for you in the alert definition wizard.
When editing an existing alert:
If you change the alert type to one that is not supported by a CAS in your installation, this server will automatically be removed from the list of devices to which the definition is published.
If you remove a server from the list of CAS instances to which the alert should be published, and the system discovers that the alert definition uses metrics that are not supported by the remaining devices, you will see a warning message listing unsupported metrics. In this situation, you have to either modify the list of servers or edit the alert detector settings so that they do not use unsupported parameters.