Study guide

15.1 OCI Monitoring: Metrics, Namespaces, Custom Metrics & Monitoring Query Language

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.1 OCI Monitoring: Metrics, Namespaces, Custom Metrics & Monitoring Query Language

Key Takeaways Explain This Topic AI

OCI Monitoring receives metrics as raw data points (timestamp-value pairs) with dimensions and metadata, from OCI resources or as custom metrics.

An MQL query must specify a metric, an interval, and a statistic, such as CpuUtilization[1m].mean() .

With a 1-minute interval, a metric query returns at most 7 days of data, while 1-hour and 1-day intervals return up to 90 days.

Custom metric namespaces cannot use the reserved prefixes oci_ or oracle_ .

Custom metrics can be posted as often as every second, but the minimum aggregation interval is one minute.

Last updated: October 2026

How Monitoring Works

The OCI Monitoring service has two features: Metrics , which collect and query measurements of health, capacity, and performance, and Alarms , which notify you when metrics meet a trigger (Section 15.2). Metric and alarm data is available from the Console, CLI, and API.

Metrics come from three sources:

Resource (service) metrics that OCI services post automatically. For example, Compute posts CpuUtilization for monitoring-enabled instances in the oci_computeagent namespace through the Oracle Cloud Agent.

Custom metrics that your applications publish with the Monitoring API, or that the Unified Monitoring Agent collects through agent configurations , such as Prometheus-format metrics exposed on an HTTP endpoint of a VM.

Connector Hub , which can move data from Logging into Monitoring as metrics (Section 16.3).

Core Concepts

  • Concept Meaning Example
  • Data point A timestamp-value pair, raw (as posted) or aggregated 2022-05-10T22:19:00Z, 10.4

Metric namespace The service or application that emits the metric oci_computeagent , oci_objectstorage , oci_redis

  • Dimension A name-value qualifier used to filter or group resourceId , availabilityDomain , faultDomain
  • Metadata Reference information such as the unit bytes for DiskBytesRead

Metric stream Aggregated data for one metric and one set of dimension values; one line on a chart CPU of one instance

  • Frequency How often raw data points are posted; most service metrics post every 60 seconds 1 per minute
  • Interval The window over which raw points are aggregated [1m] , [5m] , [1h]
  • Statistic The aggregation function applied in each interval mean() , max() , percentile(0.9)
  • Resolution How often the aggregation windows shift; for metric queries it defaults to the interval 1m

Resource group An optional custom string on a custom metric, used to filter or aggregate; one per metric divisionX

Metrics are not OCI resources and have no OCIDs. Access is controlled with IAM policies on the metrics resource type.

Monitoring Query Language (MQL)

An MQL expression always contains a metric , an interval , and a statistic , and optionally dimension filters, grouping functions, and a predicate: CpuUtilization[1m]{availabilityDomain = "VeBZ:PHX-AD-1"}.groupBy(poolId).percentile(0.9) > 85

Reading it from left to right: take CpuUtilization , aggregate it every 1 minute, keep only streams in one availability domain, group the streams by instance pool, compute the 90th percentile, and keep values above 85.

Intervals and Time Ranges

Valid intervals are 1m to 60m , 1h to 24h , and 1d . The interval determines the default resolution and therefore the maximum time range a metric query returns:

  • Interval Maximum time range returned
  • 1 minute 7 days
  • 5 minutes 30 days
  • 1 hour 90 days
  • 1 day 90 days

Pick the alarm interval based on how often the metric is emitted; a metric emitted every five minutes needs an interval of at least 5 minutes.

Statistics

  • Statistic Returns
  • mean() / avg() Sum divided by count
  • max() , min() Highest or lowest value in the interval
  • sum() All values added together
  • count() Number of observations
  • percentile(p) Estimated percentile, with p between 0 and 1, for example percentile(0.95)
  • rate() Per-interval average rate of change, per second
  • increment() Per-interval change
  • first() , last() Earliest or latest value in the interval
  • absent() True when the metric is absent for the entire interval

Each query uses one statistic per metric. For a throughput rate, write NetworksBytesIn[1m].rate() , not a chain of statistics such as .sum().rate() .

Filters, Fuzzy Matching, and Grouping

Dimension filters go in braces: {resourceId = "ocid1.instance..."} .

Fuzzy matching uses =~ with * as a wildcard and | for alternatives: {resourceDisplayName =~ "web-*|api-*"} .

groupBy(dimension) aggregates streams that share a dimension value, such as one line per instance pool.

grouping() combines all streams into a single value, such as total requests across all resources.

Predicates, Arithmetic, and Joins

Predicates : > , >= , == , != , < , <= , in (low, high) (between, inclusive), not in (low, high) , and absent() .

Arithmetic : + , - , * , / , and % . For example, 100 - CpuUtilization[1m].mean() gives idle CPU, and TotalRequestLatency[1m].mean() / 1000 converts milliseconds to seconds.

Joins : && (AND) and || (OR) combine queries. For example, ServiceConnectorHubErrors[1m].count() > 1 && ServiceConnectorHubErrors[1m].mean() > 0.5 is true only when both conditions hold.

Custom Metrics

Publish business or application metrics, such as orders per minute or failed payments, with the PostMetricData API or the CLI command oci monitoring metric-data post . Key rules:

Posting uses the telemetry-ingestion endpoint, while queries use the telemetry endpoint.

Do not start the namespace with oci_ or oracle_ .

Data points can be posted as often as every second , but the minimum aggregation interval is one minute .

Timestamps must be near the current time: less than two hours in the past and less than 10 minutes in the future .

Publishers need an IAM policy such as allow group app-publishers to use metrics in compartment apps where target.metrics.namespace = 'orders_app' .

The Unified Monitoring Agent with agent configurations is an alternative that does not need custom API code, for example to scrape Prometheus endpoints on VMs.

Limits That Affect Design

Metric definitions and alarm history are stored for 90 days .

A metric query returns at most 100,000 data points , so long time ranges need larger intervals.

An alarm tracks up to 200,000 metric streams .

Visualizing Metrics

The Service Metrics page shows default charts for each namespace, the Metrics Explorer builds custom charts from MQL, and dashboards combine widgets for operations teams. Each chart line is one metric stream unless you aggregate the streams.

Loading diagram... Monitoring Data Flow