Study guide
15.2 Alarms & Notifications: Trigger Rules, Absence Alarms, Split Messages, Suppression & Delivery
OCI 2026 Architect Professional 1Z0-997-26
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Architecture Foundations
1.1 Exam Logistics, the 2026 Blueprint & How to Use This Guide 1.2 The OCI Well-Architected Framework & Architectural Tradeoffs
2 Chapter 2: High Availability & Resilient Design
2.1 Availability Domains, Fault Domains, Instance Pools & Load Balancers 2.2 OCI DNS Traffic Steering, Geolocation & Health Checks 2.3 Block Volume Replication, Volume Groups & Backup Policies 2.4 Object Storage Replication, Versioning & Retention Rules (WORM)
3 Chapter 3: Full Stack Disaster Recovery
3.1 Full Stack Disaster Recovery: Protection Groups, Members & Permissions 3.2 DR Plans: Switchover, Failover, Prechecks & Plan Execution 3.3 DR Drills, Plan Customization & Operational Readiness
4 Chapter 4: Container Instances, OCIR & OCI DevOps
4.1 Containerization, Microservices & OCI Container Instances 4.2 OCI Container Registry: Repositories, Push & Pull, and Image Management 4.3 OCI DevOps: Code Repositories, Build Pipelines & Deployment Strategies
5 Chapter 5: OCI Kubernetes Engine (OKE)
5.1 OKE Cluster Types, Node Options & Cluster Creation 5.2 OKE Networking: VCN-Native Pod Networking vs. Flannel, Subnet Sizing & Load Balancers 5.3 OKE Workload Identity, Secrets & Persistent Storage
6 Chapter 6: Serverless Functions & API Gateway
6.1 OCI Functions: Concepts, Invocation Modes, Integrations & Image Security 6.2 API Gateway: Authentication, JWT Validation, Rate Limiting & Usage Plans
7 Chapter 7: Messaging & Event-Driven Design
7.1 OCI Streaming, OCI Queue & Messaging Patterns for Microservices 7.2 OCI Events, Event Rules & OCI Notifications Fan-Out
8 Chapter 8: Infrastructure as Code with Terraform & Resource Manager
8.1 Infrastructure as Code with Terraform and the OCI Provider 8.2 OCI Resource Manager: Stacks, Jobs, Drift Detection & Private Endpoints
9 Chapter 9: Identity & Multi-Tenancy Governance
9.1 IAM Policy Design: Verbs, Conditions, Dynamic Groups & Principals 9.2 Organizations Management, Governance Rules & Compartment Quotas
10 Chapter 10: Security Posture with Cloud Guard & Security Zones
10.1 Cloud Guard: Detector Recipes, Problems, Scores & Responders 10.2 Security Zones & Vulnerability Scanning
11 Chapter 11: Secure Access & Network Protection
11.1 Layered Network Security: Security Lists, NSGs & Private Access to Services 11.2 OCI Bastion: Managed SSH, Port Forwarding & SOCKS5 Sessions 11.3 Zero Trust Packet Routing (ZPR): Security Attributes & Intent-Based Policy 11.4 OCI Network Firewall: Policies, Inspection Routing, Tunnel Inspection & Private NAT
12 Chapter 12: Application & Data Protection: WAF, Certificates & Vault
12.1 OCI Web Application Firewall: Policies, Modules, Actions & Enforcement Points 12.2 OCI Certificates: Private CAs, TLS Certificates, Renewal & Integrations 12.3 OCI Vault Key Management: Vault Types, Protection Modes, Dedicated KMS & External KMS 12.4 Vault Secrets: Versions, Rotation States, Automatic Generation & Rotation
13 Chapter 13: Base Database Service & Autonomous AI Database
13.1 Base Database Service: DB Systems, RAC, Data Guard, Cloning & Maintenance 13.2 Autonomous AI Database: Workload Types, Deployment Options, Services & Connectivity 13.3 Operating Autonomous AI Database: Scaling, Cloning, Backups, Patching & Self-Tuning 13.4 Autonomous Data Guard & Backup-Based Disaster Recovery for Autonomous AI Database
14 Chapter 14: Recovery Service, Global Distribution & OCI Cache
14.1 Autonomous Recovery Service: Protection Policies, Real-Time Protection & Retention Lock 14.2 Globally Distributed Autonomous AI Database: Sharding, Data Placement & Replication 14.3 OCI Cache: Valkey and Redis Clusters, Sharding, Security & Cross-Region Replication
15 Chapter 15: Monitoring, Alarms & Notifications
15.1 OCI Monitoring: Metrics, Namespaces, Custom Metrics & Monitoring Query Language 15.2 Alarms & Notifications: Trigger Rules, Absence Alarms, Split Messages, Suppression & Delivery
16 Chapter 16: Logging, Audit, Connector Hub & Search
16.1 OCI Logging: Log Groups, Service Logs, Custom Logs & the Unified Monitoring Agent 16.2 Logging Search, the Logging Query Language & OCI Audit 16.3 Connector Hub: Moving Logs, Metrics, Queue Messages & Streams Between Services 16.4 OCI Search with OpenSearch & Resource Search for Observability
15.2 Alarms & Notifications: Trigger Rules, Absence Alarms, Split Messages, Suppression & Delivery
Key Takeaways Explain This Topic AI
OCI Monitoring evaluates every alarm once per minute.
An alarm can have up to two trigger rules, for example a critical rule at 95% CPU and a warning rule at 90% CPU.
The trigger delay (pendingDuration) is how long the condition must persist before an alarm moves to the FIRING state.
An absence alarm uses a default absence detection period of two hours, configurable from one minute to three days.
An alarm can send at most 60 messages per evaluation to a Notifications topic and up to 100,000 to a Streaming stream.
Last updated: October 2026
What an Alarm Contains
An alarm is an MQL alarm query plus the notification destination to use when it fires. Its main properties:
- Property Purpose Example
- Metric namespace and query The MQL expression, including the trigger rule CpuUtilization[1m].mean() > 90
Trigger rule The condition (threshold or absence), its severity , trigger delay , and body Severity CRITICAL , delay PT5M
Severity Critical, Error, Warning, or Info Critical for outages, Warning for early signs
Body Human-readable guidance, which can include runbook links and dynamic variables such as {{query}} "High CPU. Follow runbook step 3."
Destination A Notifications topic or a Streaming stream ops-critical topic
Message grouping Group all metric streams into one message, or split per metric stream Split for per-server alerts
- Message format Raw, pretty JSON, or formatted (ONS optimized) Formatted for email
- Repeat notification Re-send while the alarm stays firing Every 1 hour
An alarm can have up to two trigger rules , so one alarm can send a Warning at 90% and a Critical at 95%.
How Evaluation Works
Monitoring evaluates each alarm once per minute . For alarm queries, the only valid resolution is 1m , while the interval in the query (for example [5m] ) sets the window that each data point aggregates.
The trigger delay ( pendingDuration ) sets how long the condition must hold before the alarm fires. Consider CpuUtilization[1m].percentile(0.9) > 85 with a trigger delay of 3 minutes: the alarm moves to FIRING only after three consecutive one-minute evaluations are true. It returns to OK when the breaching condition has been clear for the most recent minute. A trigger delay filters out short spikes, which is the main lever for reducing noise.
Updates to an alarm can take up to five minutes to take effect everywhere.
Threshold and Absence Alarms
A threshold alarm fires when a metric value crosses a limit, for example memory above 85%.
An absence alarm uses absent() and fires when a metric stops arriving, which often means an agent, instance, or application has stopped reporting. The absence detection period defaults to two hours and can be set from one minute to three days .
When a metric stream that caused the alarm to fire stops reporting, Monitoring starts an internal reset period of 10 minutes . If the stream stays absent for that whole period, the alarm stops evaluating it and can send a RESET message. A RESET means you should check the health of the resource, because it may have stopped emitting data rather than recovered.
Alarm States and Message Types
- Message type When it is sent
- OK_TO_FIRING The alarm moves from OK to FIRING
- FIRING_TO_OK The condition clears
- REPEAT The alarm stays FIRING and repeat notifications are configured
- RESET The alarm returns to OK after one or more internal resets
- Grouped Versus Split Notifications
Grouped : one message describes all metric streams that meet the condition. This is good for a fleet-wide view, such as "4 instances above 90% CPU".
Split per metric stream : Monitoring evaluates each metric stream separately and sends a message for each one that changes state. This is good for routing a ticket per server. The dedupekey field helps receivers group messages for the same alarm and stream.
Split messages are subject to destination limits per evaluation: up to 60 messages for a Notifications topic and 100,000 for a Streaming stream . Extra messages are dropped. An alarm tracks up to 200,000 metric streams . For large fleets that need per-resource messages, use a stream as the destination, or use grouped messages.
Suppressions
A suppression stops an alarm from publishing messages during a time range, such as a maintenance window. Suppressions can apply to the whole alarm or to specific dimensions , for example only the instance being patched, and you can suppress several alarms at once. The alarm definition stays unchanged; only its messages stop until the suppression ends, which is safer than disabling or deleting alarms and forgetting to restore them.
Notifications Topics and Delivery
The usual destination is an OCI Notifications topic. Its subscriptions fan the alarm out to email, Slack, PagerDuty, SMS, HTTPS endpoints, or Functions (Section 7.2). Notifications delivers at least once per subscription and retries failed deliveries, so receivers should be idempotent. A function subscription can run automated remediation, such as scaling an instance pool or collecting diagnostics.
When a single topic or stream serves many alarms, it can be overused and delay notifications. Oracle recommends separate topics or streams for high-volume alarms, enough stream partitions for the expected load, and higher tenancy limits when needed.
Designing Useful Alarms
Alert on symptoms users feel , such as API Gateway 5xx errors or latency, and use resource metrics for diagnosis.
Use trigger delays to ignore brief spikes, and two trigger rules for early warning and real problems.
Add absence alarms for critical metrics so silent failures are noticed.
Write bodies that tell the on-call engineer what to do, with runbook links.
Route by severity : Critical to paging, Warning to chat or email.
Apply suppressions during planned maintenance instead of disabling alarms.