|Oracle® Enterprise Manager Cloud Control Upgrade Guide
12c Release 2 (22.214.171.124)
Note:This appendix is applicable only if you are upgrading from Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) or Enterprise Manager 11g Grid Control Release 1 (126.96.36.199).
Prior to Enterprise Manager Cloud Control, the notification system notified administrators of target availability status changes, metric alerts, and status changes of job executions. In addition to notifying the administrators, the notification system performed actions such as running operating system commands, including scripts, and PL/SQL procedures when an alert was triggered.
This appendix describes how the notification system has changed significantly in Enterprise Manager Cloud Control. In particular, this appendix covers the following:
In the earlier releases of Enterprise Manager, the notification system operated using Notification Rules, which were a set of predetermined rules or conditions indicating when a notification had to be sent and what actions had to be taken.
Before discussing Incident Rulesets, understand the concept of Events and Incidents.
Events are significant and interesting occurrences in your managed environment. Target availability status changes, metric alerts, and status changes of job executions are examples of the types of events that Enterprise Manager detects. Users may be interested in getting notified about these events and responding accordingly to resolve the underlying issues. By formalizing the concept of events, Enterprise Manager extends the monitoring functionality to additional occurrences in the enterprise that might be of interest, such as metric evaluation errors or compliance standard violations.
Incidents are a subset of related events that may indicate potential or actual disruption to the dependent IT services, and require attention from an administrator or a team. Incidents can be created for such events, which can then be assigned to an administrator and tracked to completion.
Incident Ruleset is a set of rules that typically operate on a set of targets, and include individual rules to notify appropriate personnel and take appropriate action on events, incidents, and problems.
Note:For information about the problems, refer to the Oracle Enterprise Manager Administrator's and User's Guide available in the Enterprise Manager documentation library at:
A rule can operate on events to send notifications as well as create incidents. It can also operate on specific incidents, so you can auto-assign, prioritize, or even escalate them via time-based conditions.
Enterprise Rulesets are used to automate and enforce enterprise level behavior such as notifying one or more users, sending notifications using advanced notification methods, raising tickets in external ticketing systems, creating and updating incidents. Only administrators with the Create Enterprise Ruleset privilege can create these rulesets.
All Incident Rulesets can be edited by the owner of the ruleset and any super administrator. In addition, the owners can designate other users as coauthors of Enterprise Rulesets. This enables shared management of the ruleset.
To view all Incident Rulesets, in Enterprise Manager Cloud Control, from the Setup menu, click Incidents, and then, select Incident Rules. Figure B-1 shows the Incident Ruleset page:
During upgrade, all Notification Rules created in the earlier release of Enterprise Manager are automatically migrated to corresponding Incident Rulesets that act on the targets originally defined in the Notification Rule.
The following Notification Rules are migrated to Enterprise Rulesets:
Notification Rules that send e-mails to owners who have not created the rules
Notification Rules that invoke an advanced notification method
The following Notification Rules are migrated to Private Rulesets:
Notification Rules that have no actions.
Notification Rules that send e-mails to owners who have created the rules.
Each of the three possible criteria—availability, metrics, jobs—defined in an old Notification Rule are migrated to three individual rules that operate on appropriate events. The action defined at the Notification Rule level is copied over to each of these rules.
One exception is that the concept of Policy Violations is being withdrawn in Enterprise Manager Cloud Control, and therefore, all policy-specific criteria are ignored and none of the rules that solely operate on policies are migrated.
The owners of Notification Rules, which were created in the earlier release of Enterprise Manager, become the owners of the corresponding Incident Rulesets in Enterprise Manager Cloud Control. These owners can edit the Enterprise Rulesets and Private Rulesets. In addition, all administrators can create Private Rulesets to send e-mails to themselves.
Going forward, the super administrators should determine which administrators can create Enterprise Rulesets by granting the Create Enterprise Ruleset resource privilege.
Note:For situations where the target type modeling has changed in Enterprise Manager Cloud Control, you must manually adjust the rules as described in Updating Incident Rules.
Notification methods and actions defined in earlier releases of Enterprise Manager will continue to work in Enterprise Manager Cloud Control, and the input to these original notification methods are backward compatible in Enterprise Manager Cloud Control. So if you had an OS command or a PL/SQL notification method that operated on metric alerts, you will continue to receive the same input after upgrade. However, all new notification methods you create in Enterprise Manager Cloud Control will accept input based on the new event and incident model.
Note:Oracle strongly recommends you to replace the Notification Methods created in the earlier releases of Enterprise Manager with the new Enterprise Manager Cloud Control-specific notification methods that operate on the new event model. With the next major release of Enterprise Manager Cloud Control, the older notification methods will no longer function.