Study guide

16.3 Connector Hub: Moving Logs, Metrics, Queue Messages & Streams Between Services

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.3 Connector Hub: Moving Logs, Metrics, Queue Messages & Streams Between Services

Key Takeaways Explain This Topic AI

A Connector Hub connector defines a source service, optional tasks, and a target service, and connectors run continuously.

Connector Hub sources are Logging, Monitoring, Queue, and Streaming.

The log filter task is available only for a Logging source, while a Functions task can process data from any source except for a few Notifications combinations.

Connector Hub delivers each batch at least once and retries a failed move before moving later batches.

Messages larger than 128 KB sent to a Notifications target are dropped.

Last updated: October 2026

What Connector Hub Does

Connector Hub , formerly Service Connector Hub , is a cloud message bus for moving data between OCI services. Instead of writing and running code to copy logs to a bucket or forward metrics to a SIEM, you define a connector :

Source : where the data comes from.

Tasks (optional): a log filter task to select log entries, or a Functions task to transform data.

Target : where the data goes.

Connectors run continuously , and data moves in a sequence of move operations. Delivery speed depends on the source, task, target, and their service limits. For example, a Logging-to-Notifications move takes up to a few minutes, and a Streaming source with a Functions task and Object Storage target can take up to about 17 minutes depending on batch settings.

Sources and Targets

  • Source Functions Log Analytics Monitoring Notifications Object Storage Streaming
  • Logging Yes Yes Yes Yes Yes Yes
  • Monitoring Yes No No No Yes Yes
  • Queue Yes No No Yes, without a Functions task Yes Yes
  • Streaming Yes Yes No Yes, without a Functions task Yes Yes

Targets behave differently: Functions processes data; Log Analytics, Monitoring, Object Storage, and Streaming store it; and Notifications delivers it to topic subscriptions.

Source Details

Logging : select one or more logs or log groups, including the _Audit log group. The Logging source has a 24-hour retention period in Connector Hub.

Monitoring : select metric namespaces in one or more compartments; metric data points are aggregated before delivery. Retention is also 24 hours.

Queue : messages are written to the target and then automatically deleted from the queue.

Streaming : retention is the stream's own retention period, which you define.

Tasks

The log filter task is supported only for a Logging source . It uses the Logging query syntax, a search scope plus a where condition, such as entries whose data.statusCode is 500 or higher. It does not use JMESPath or SQL.

A Functions task sends batches to a function for custom processing, such as masking personal data, enriching records, or converting formats. The task returns processed data to Connector Hub, which writes it to the target. A Functions task is not supported for Queue or Streaming sources with a Notifications target.

Delivery, Retries, and Batching

Connector Hub follows at-least-once delivery : each batch is delivered at least once, so targets may see duplicates and should handle them.

If a move fails, the connector retries it and does not move later batches until the retry succeeds.

If failures continue beyond the source's retention period , that batch is not delivered. For Logging, data generated more than 24 hours earlier can be skipped after a long outage.

The Notifications target accepts messages up to 128 KB ; larger messages are dropped.

Batch settings exist for a Functions task , Functions target , and Object Storage target . You can set a batch size and a batch time , and whichever limit is reached first triggers the flush. For example, with 1 MB and 10 seconds, a batch is sent when 1 MB has accumulated or 10 seconds have passed.

Failing and Updated Connectors

A connector that keeps failing with 404 errors , or 502 errors from a function, triggers a warning announcement after four consecutive days and is automatically deactivated after seven days . Fix the configuration and reactivate it, and enable connector logs to see the data flow.

Updating a connector's source, task, or target resets it internally , so it may not resume from its previous position and may reprocess data. Oracle recommends creating a new connector when the source or target must change.

IAM for Connectors

A connector acts as its own principal ( request.principal.type = 'serviceconnector' ). When you create or edit a connector in the Console, default policies are offered for its source, task, and target. For example, an Object Storage target gets: Allow any-user to manage objects in compartment id <bucket_compartment_ocid> where all {request.principal.type='serviceconnector', target.bucket.name='<bucket_name>', request.principal.compartment.id='<connector_compartment_ocid>'}

For narrower access, create a dynamic group that matches connectors, such as All {resource.type = 'serviceconnector', resource.compartment.id = '<compartment_ocid>'} , and write policies for that dynamic group. A Logging source has no default policy: the person creating the connector needs read access to the logs. Automatically created policies remain after a connector is deleted, so delete them as part of cleanup.

Common Designs

Requirement Connector design

Keep logs for years for compliance Logging source (including _Audit ), Object Storage target, plus bucket lifecycle rules to Archive storage

Alert on specific log events Logging source, log filter task, Notifications target

Count log events as a metric for alarms Logging source, log filter task, Monitoring target, then an alarm on the new metric

  • Send security events to an external SIEM Logging source, Streaming target; the SIEM consumes the stream
  • Mask personal data before archiving Streaming or Logging source, Functions task, Object Storage target
  • Export metrics for long-term analysis Monitoring source, Object Storage target
  • Process queue messages with code Queue source, Functions target
  • Design Example: Alerting on IAM Policy Changes

A security team wants an email whenever someone creates, updates, or deletes an IAM policy:

Create a connector with the Logging source set to the _Audit log group of the relevant compartments.

Add a log filter task whose where condition matches the policy event types, for example a type containing identitycontrolplane and policy .

Set the target to a Notifications topic with an email subscription for the security team.

Accept the default policy offered for the topic.

To count changes over time instead of sending one email per event, send the filtered entries to a Monitoring target and create an alarm on the resulting metric.

Loading diagram... Connector Hub Data Flow