IOUG Collaborate 2014 Mastering EM12c Monitoring

Mastering Enterprise
Manager 12c Monitoring
Kellyn Pot’Vin
Consulting Member of Technical Team
Strategic Customer Program

Who Am I?
 Former ACE Director, Oak Table member, RMOUG board liaison
 Passionate about mentoring and furthering opportunities for women in
technology.
 Author and presenter at Oracle Open World, HotSos, Collaborate,
KSCOPE and others…
 Live in Westminster, northwest of Denver, CO.

What We’ll Tame Today
 The Enterprise Manager 12c, (EM12c) environment!
– Target Management
– Incident Management
– Building Effective Rule Sets
– Creating Administration Groups
– Reporting
– Why Centralize Environment Job Management

EM12c Architecture at a Glance
OMS

Oracle
Database
OMS

Oracle
Database
OMS
Console
EM CLI

Oracle
Database
OMS
Console
EM CLI
Agent
Agent
Agent

Targets- All Shapes and Sizes…
 Host
 Database
 Listener
 Cluster
 ASM
 Oracle Home
 Weblogic components
 HTTP Server
 OMS Components
 Etc, etc…

EM12c Mastering
 Auto-Discovery
 Monitoring Templates
 Incident Rule Sets
 Incident Management
 Groups/Admin Groups
 Summary

Auto Discovery
 A way for EM12c to automatically search environment for
targets.
 Must be set up in EM

 Main Targets are ready to be configured, simple set up via the
console.

Configuring Auto-Discovery

Inspecting Overall Discovered Targets

Target Links
Discovered Targets
Managed Targets

Discovered Targets
 From Setup, Add Target, Auto-Discovery Results
 Click on discovered targets, click on target and click on Promote.

Monitoring Templates
 Sets distinct, consistent monitoring for individual targets or
groups.
 Still allows for individual metric policies and thresholds to be set
and not overridden by templates.
 Easy to maintain and can be automated to be set as “default”
template for targets/groups.

Creating a Monitoring Template
 Or part of administration group creation step.

Monitoring Template Design
 Base Templates off Existing Targets
 Build by Target Type
 Make Templates DEFAULT for Crucial Target Types.

Incident Rule Sets
• Two Default Rule Sets
• “Create Like” for the Default Rules Sets
• Build out New Ones
• Disable the Defaults

A Rule Set Can…..
 Be assigned to a Target, Target Type or a GROUP.
 Build out rule sets as complete as you need.

Rules
 Think about…
– What is important to be ACTUALLY notified for?
– What is TRULY mission critical?
– What should be managed during the business day?
– More notifications are NOT better notifications
– No, NO WHITE NOISE- make every notification count.

Defining Rules for Efficiency
 From default rule, but have eliminated all categories but Availability and
Capacity that are Critical.
 Email who is required to be notified AND
 Set the owner and the priority in the incident.

The Rest of the Categories
 Created a second rule
– Still severity has to be critical
– Covers all categories removed from original rule.
– No email notification- I want these to just create an incident.
– Sets the owner and the priority automatically.

Auto-Clear of Metric Rules
 Update how long till auto-clear
 Remove notification- no, I don’t want an email!

What about Warnings??
 No, there aren’t any rules set for warnings.
 I choose to use the incident manager to track warnings and pro-
actively manage from it.
 Severity Warning, creates and incident, sets the owner to SYSMAN
and priority to LOW.
 This is a PROFESSIONAL PREFERENCE.

When to Know to Change a Rule
 Notification does not provide value.
 Notification is triggered by a bug, isn’t critical or can’t be resolved by
the one notified.
 Always retain the email notification to ensure you are editing the
correct notification.
 Break down the rule to ensure that metrics grouped in one category
are not mistakenly set to not notify.

Everything You Need….

Edit the Rule from the Rule Set..

Search the Target Type and Metric

Add the Device to Exclusion List

Tips on Event Building
 Create New Rules and Break Down Categories
 Inspect Each Notification the Impacts Effective Alerting.
 Recognize when a metric threshold vs. a rule set is the “culprit”.

Edit Actions
 Choose if this should be done for all actions.
 Create Incident, automatically assign.
 Set a priority and even update information automatically in the incident.

Editing Actions, Cont.

Review Rule and Rule Sets

Incident Management
 Critical Notifications are now ONLY for Mission Critical and
Production Down
 The Incident Manager interface now can be utilized for review and
management.

An Incident
High Level Information regarding incident and links to details.

Incident Events
Steps covered in incident and escalation.

Incident Updates
 Steps through the updates to the incident.
 If any notifications have been sent, this is where you look!

Editing Thresholds for Incidents
 If Metrics Involved, Edit from Incident:

Set New Thresholds

Threshold Suggestions

Set the New Metric Thresholds
 Suggestions Have Verified- no Guessing.
 Upped Number of Occurrences to Eliminate False Alerts
 Choose if Monitoring Templates Can Override.

Groups and Admin Groups
 Groups ease management of targets, allowing assignment of tasks,
monitoring and other features through a single alias for multiple
targets.
 Groups are still supported, but limited vs. what Administration groups
offer you. The one advantage is multiple group assignment of a single
target.
 Administration groups set hierarchy and automate management by
assigning monitoring templates, compliance standards, and cloud
policies.

Groups- Simple
 Creating Groups are like Creating Roles…
 Add targets to a group or more than one group at any time.
 Edit standard groups down the road.
 Groups can be used with rule sets to assign alerts to multi-level
escalation in actions.

Administration Groups- Complex
 Plan out first, including “Line of Business”, “Lifecycle Status” and
what types of databases exist in environment, (production, mission
critical, staging, development, QA, etc.)
 Once created, most design elements of the Administration group
are not open to edits.
 All hierarchy for each target is available in the “target properties”.

Setting up Admin Groups
 Click on Targets, Groups OR Setup, Add Target, Administration Groups
 Create, Choose Administration Group
Have your design ready…

Creation a Hierarchy
 Start with Lifecycle Status
 Decide which to keep, edit, add, remove or merge.

Create Your Line of Business
 Click on “Add” in Hierarchy Levels, (again)
 Choose Line of Business, click on Add, separate by a comma all lines
of business desired.

Simple Hierarchy is now built
 Development Hierarchy, (same for each Lifecycle status)

Create Hierarchy
 Click on Create, warning will appear-

 Monitoring Templates, (covered earlier), can be created as part of
this step.
 Compliance and Cloud standards must be created in the
appropriate framework in EM12c before being added to the
Administration Group.

Create and Choose Existing

Create the Template Collections
 Add all monitoring templates required of any life cycle.
 Note- No associations exist yet!

Run Unassociated Target Report
 Run Report to see what targets aren’t associated with Admin Groups.

Editing a Target
 Fill in all Pertinent Information

Post Association
• Associate Template Collection
• Continue with all Targets Till
Complete.

Dynamic Groups
 High Level Review

Define the Membership Criteria

Reviewing the Build
 The Membership can now easily build out from the criteria entered.
 Saves from having to build Admin Groups.

Charts
 Use Default Charts to Begin

Keep it Simple
 Use Default for Charts, Columns, Dashboard

Group Review
 Dynamic Easier, Fluid
 Administration- more complex, but open to more errors.

Summary-How This Works Together
 Automate-
– Monitoring Templates
– Rule Sets
– Dynamic Groups over Administration Groups
 Efficiency
– Remove notifications that create “white noise”.
– Update metric thresholds.
– Silence metrics that offer no value.

Connect with Me on Social Media

IOUG Collaborate 2014 Mastering EM12c Monitoring

More Related Content

IOUG Collaborate 2014 Mastering EM12c Monitoring