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

Instead of setting these properties to each individual entity-database, listener, and so on you can benefit from
an enhancement which allows you to propagate the properties to members. In other words, simply update the target
properties for the members of your systems and specify the -propagate_to_members flag. Note that assigning a
lifecycle status is optional; if you would like to exclude targets from the Administration Group then simply do not add
any extra properties.

Create the Administration Group Hierarchy
Setting properties for targets as just explained is the first step towards creating an administration group. In the next
step you will see how to complete the first task, the creation of the hierarchy. Even though there are only a few clicks
to be made, the effect is far reaching: once created, it is impossible to change the hierarchy as such and it will have to
be recreated if you realize later that it has not taken all factors into account. Begin the creation of the administration
group by navigating to Targets ➤ Groups. From the “Create” button select “Administration Group” from the list of
values in the drop-down menu. Note that if there is a group defined already it will take you there straight away. In
other words the system only allows for one Administration Group.
Begin the definition of the hierarchy using the tab with the same name. There won't be a hierarchy initially, so
click on the “Add” button on the left-hand side to create one. The initial—and only—hierarchy level in this example
will be the lifecycle status. The different statuses are then displayed in the Hierarchy Nodes pane in the lower left of
the screen. If you do not like the short names you can make use of the pencil icon to change them. The “Calculate
Members” button is a convenient way to preview how many targets fall into a given category. This of course requires
that you defined the extended attributes to the targets as discussed earlier.
You may want to add further levels to the hierarchy to represent your organization more accurately. Simply repeat
the initial step for every additional level you want to add. When you are happy with the definition of your hierarchy,
click on the “Create” button to save the configuration to the repository.

■ Caution Do not switch tabs without saving the hierarchy or all changes will be lost.

Define Template Collections
Template collections group multiple monitoring templates together. Monitoring templates exist for each monitored
target (agent, database, . . .) and are key to a centralized and standardized monitoring. With their use you define on
a per-target type basis what should be monitored. Enterprise Manager comes with lots of templates out of the box,
accessible via Enterprise ➤ Monitoring ➤ Monitoring Templates. If you would like to have a look at what they do,
simply limit the target type to what you would like to monitor and then execute a search. To view the Oracle provided
templates you need to check the box named “Display Oracle Certified templates”.
Pick a template from the search result and click on the template name to view its definition. The tab named
“Metric Thresholds” shows what the template monitors for. You will notice that a monitoring template is not limited to
a single metric. Any metric gathered by the agent can be used in the monitoring template, it is up to the administrator
to decide which metrics are important for his business area.

■ The creation of metric templates is out of the scope of this chapter. please refer to the official Enterprise
Manager documentation “Cloud Control administrators guide” Chapter 7 “Using Monitoring Templates” for more
information about creating and maintaining monitoring templates.

Note