Study guide

16.1 OCI Logging: Log Groups, Service Logs, Custom Logs & the Unified Monitoring Agent

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

16.1 OCI Logging: Log Groups, Service Logs, Custom Logs & the Unified Monitoring Agent

Key Takeaways Explain This Topic AI

OCI Logging handles three kinds of logs: audit logs, service logs, and custom logs.

Each log in OCI Logging is a resource with its own OCID, and every log belongs to a log group in a compartment.

Custom logs can be ingested with the Logging Ingestion API (PutLogs) or with the fluentd-based Unified Monitoring Agent.

Instances that send custom logs through the agent need a dynamic group and a policy such as allow dynamic-group app-fleet to use log-content in compartment apps .

Object Storage read and write log categories capture object-level access events that the Audit service does not record.

Last updated: October 2026

Why Centralized Logging Matters

When an incident happens, architects need to answer questions like "which client called this API?", "what did the load balancer return?", and "what did the application log just before it failed?". OCI Logging is a fully managed, highly scalable service that gives you a single place to enable, manage, and search the logs from OCI resources, applications, other clouds, and on-premises systems.

The Three Kinds of Logs

Kind Source How you get it

Audit logs The Audit service, which records API calls to public OCI endpoints Always on; read-only; shown on the Audit page and in Search as the _Audit log group (Section 16.2)

Service logs OCI services such as API Gateway, Events, Functions, Load Balancer, Object Storage, and VCN Flow Logs Enable a log category on each resource

Custom logs Your applications, other clouds, or on-premises systems Unified Monitoring Agent or the Logging Ingestion API

Logs and Log Groups

A log is a first-class OCI resource with an OCID . For example, enabling flow logs on a subnet creates a dedicated log.

A log group is a logical container for logs in a compartment. You must create one before you enable a log. Use log groups to apply IAM policies and to search related logs together, such as one log group per application or environment.

Moving a log group to another compartment moves all of its logs with it.

Logs are encrypted in flight during ingestion, encrypted at rest, and encrypted when archived. Only UTF-8 text is supported.

Retention

For service and custom logs, you choose the retention period in 30-day increments up to 180 days . For longer retention, such as compliance archives kept for years, use Connector Hub to copy logs to Object Storage (Section 16.3).

Service Logs and Log Categories

Each service defines its own log categories , which are unrelated to other services' categories:

  • Service Example categories Typical use
  • Object Storage Read and write access events for a bucket Who downloaded or uploaded which object
  • Load Balancer Access and error logs Request status codes and backend errors
  • API Gateway Access and execution logs Per-request API details and policy decisions
  • Functions Function invocation logs Application output from functions
  • VCN Flow Logs Accepted and rejected traffic records Troubleshooting security list and NSG rules
  • Events Rule execution logs Checking event delivery

To enable a service log on a resource, you need permission on the log group and the update permission on the resource, which for many resources comes with the use verb. For example, users who can use buckets in a compartment can enable logging on those buckets.

Object Storage Logs Versus Audit

The Audit service records bucket-level API calls, such as creating a bucket or changing its visibility, but not object-level operations such as GetObject or PutObject . To answer "who downloaded this file?", enable the bucket's read log category, and its write category for uploads.

  • Custom Logs
  • Unified Monitoring Agent

The Unified Monitoring Agent is a fluentd-based agent that runs on OCI instances, delivered as the Oracle Cloud Agent plugin called Custom Logs Monitoring , which must be enabled on the instance. It works on both VM and bare metal instances.

An agent configuration tells the agent what to collect:

Host groups : the dynamic groups (or groups) of instances that use the configuration.

Log inputs : Log Directory (Tail) file paths, such as /var/log/app/*.log , or Windows Event Logs .

Parser : how to turn lines into structured fields, for example none, JSON, regular expression, multiline, syslog, or Apache formats.

Destination : the custom log that receives the entries.

Any log field longer than 10,000 characters is truncated during ingestion. Agent configuration updates are detected and loaded automatically. The same agent can also collect custom metrics , such as Prometheus endpoints, for Monitoring.

IAM for Agents

The instances must be in a dynamic group , and a policy must let that group get configurations and send logs: allow dynamic-group app-fleet to use log-content in compartment apps

With use log-content , the instances can download their configuration, push logs, and search logs. Readers who only need to view logs get read log-content , which covers service and custom logs alike.

The Logging Ingestion API

Applications, other clouds, and on-premises systems can send entries directly with the PutLogs operation of the Logging Ingestion API , which uses an ingestion.logging.<region> endpoint. This is useful for containers, serverless code, or systems where installing the agent is not possible.

Logging APIs

Logging Management API : create and manage logs, log groups, and agent configurations.

Logging Ingestion API : send custom log entries (PutLogs).

Logging Search API : search logs programmatically (Section 16.2).

Design Example: A Three-Tier Application

Create a log group per environment, such as prod-app-logs .

Enable Load Balancer access and error logs , API Gateway access and execution logs , and VCN flow logs on the application subnets.

Enable the Custom Logs Monitoring plugin on the application instances, add them to a dynamic group, and create an agent configuration that tails /var/log/app/*.log with a JSON parser.

Enable Object Storage write logs on the upload bucket.

Use Connector Hub to archive everything to Object Storage for one year, and to raise alarms on error patterns.

Loading diagram... Log Sources Flowing Into OCI Logging