Monitoring the Hosting Platform - Expert Consolidation in Oracle Database 12c - page 312

performed in the Administration Group wizard. You can now switch to the group homepage and verify the status of
its members. The great thing about the newly configured Administration Group is that targets join the group instantly
when their extended properties are set. By joining the Administration Group the templates defined in the template
collection will apply to the target, ensuring that monitoring is uniform and standardized. Assigning the target
properties can be done at target provisioning time as part of the standard deployment scripts.

Incident Management
Incident management builds upon settings and configuration steps explained in previous sections. One almost
imperative task is the creation of Administration Groups, and more specifically the definition of monitoring templates.
After your important systems are properly configured for standardized monitoring then the next step is to define
alerting. Elaborate workflows can be designed in Enterprise Manager, and if you like you can use OEM as your only
incident management solution.
Oracle however knows that many organizations already have some kind of Trouble Ticket System (TTS) in place,
and provides connectors for the most commonly used ones. Enterprise Manager collects metrics from targets. Lots
of metrics are collected, such as CPU usage, database free space, and many more. In addition, OEM records when a
target is down or a job did not execute successfully. The management agents also make extensive use of the Automatic
Diagnostic Repository (ADR) to detect problems with a listener, ASM, or database instance. This section is about using
Enterprise Manager 12c for the complete workflow. The workflow is based on notifications which you need to set up first.

Set up Notifications
Notifications—as their name implies—will inform you about events collected by the Enterprise Management
infrastructure. The most common notification method in today's IT world is electronic mail, even though it has its
flaws. Configuration of email notifications happens in two steps. The first is globally applicable and defines your
email gateway.
Navigate to Setup ➤ Notifications ➤ Notification Methods. The screen is fairly self-explanatory. If you want to
follow the example you need to specify the name of the outgoing mail server and connection details. If your Mail
Transfer Agent supports encryption you should by all means make use of the TLS or SSL options. After supplying the
required information you should click on the “Apply” button followed by a click to the “Test Mail Server” button.

■ There are many more configuration options to explore like the email format and a notification schedule. please
refer to Chapter 4 of the Cloud Control administrator's guide for all the detail about notifications, including notification
beyond email.

Note

Use Incident Management
To better understand the concept of incident management in Enterprise Manager it is important to understand some
terminology first.

• Event : An event is raised by the management framework when something happens out of the
ordinary. A metric violation can cause an event to be raised for example, or if a target goes
down outside of a pre-defined maintenance window.

• Incident : Similar events are grouped together to form an incident. Although you can have
some cases where a significant event causes an incident to be created. Enterprise Manager
tries to reduce the number of notifications by aggregating related events into a single incident.