Service Connector Hub and Alarms/Notifications
The Service Connector Hub and alarms/notifications domain tests data movement and alert delivery. Service Connector Hub moves records from a source to a target, optionally through a filter task. Common sources are Logging and Streaming; common targets are Object Storage, Streaming, Functions, and Logging Analytics. A connector is regional and runs with a service principal, so it needs IAM policies that let it read the source and write the target. Filter tasks drop records before they reach the target; batching controls object size and latency.
Alarms and ONS
Alarms evaluate Monitoring queries and publish to ONS topics. A topic has subscriptions with protocols such as email, SMS, HTTPS webhook, PagerDuty, Slack, and Oracle Functions. Email subscriptions must be confirmed. Alarm settings that matter: severity, pending duration, repeat notification interval, and message format. Alarm suppression silences notifications during a maintenance window without deleting the alarm.
Worked example
You must archive audit logs in Object Storage but only for denied actions. Create a bucket, create a connector with source Logging (the audit log), add a filter task that keeps denied events, set the target to Object Storage, and grant the connector service principal read on the log group and write on the bucket. Reasoning: the filter reduces storage and noise; the service-principal policy is mandatory; batching affects how quickly objects appear.
Traps
Forgetting the service-principal policy; placing source and target in incompatible regions; writing a filter that drops everything; assuming an unconfirmed email subscription works; and setting repeat notifications so aggressively that the team ignores the alarm.