Using Oracle Enterprise Manager Cloud Control 13c Ed 2 — Lesson 2: Metrics, Thresholds, Incidents, Notifications, and Blackouts

Technical Scope

• metric collections and baselines
• warning and critical thresholds
• incidents, rules, notification, and escalation
• blackouts, maintenance windows, and suppression

Instructor Demonstration

Demonstrate metric collections and baselines inside a database application stack onboarded, monitored, tested, and operated from a central control plane, then capture the exact configuration, command, transaction, report, or code evidence that proves the result.

Applied Workshop

Implement a controlled workshop covering warning and critical thresholds and incidents, rules, notification, and escalation, then test a failure or exception involving blackouts, maintenance windows, and suppression.

1. Confirm environment, identity, data, dependencies, and expected result.
2. Complete the product-specific implementation or analysis.
3. Capture commands, configuration, output, logs, transactions, or reports.
4. Explain the operational, security, performance, or business trade-off.

Validation Standard

The Metrics, Thresholds, Incidents, Notifications, and Blackouts result must be reproducible, traceable to approved inputs, and consistent with the expected Oracle product behavior.

• The intended target and ownership are verified.
• The result is supported by reproducible evidence.
• Security, performance, reliability, and support impact are reviewed.
• Unexpected behavior is investigated before acceptance.

Failure Analysis

Diagnose issues in metric collections and baselines, warning and critical thresholds, incidents, rules, notification, and escalation, or blackouts, maintenance windows, and suppression without making an unverified production change.

Learners isolate the smallest proven cause, apply a reversible correction, rerun validation, and record the preventive action.