Common use cases include:

• Cheap, long-term data archival: Service Connector Hub integrates with Object Storage to move data for cheap, long-term archival.
• Integrate with third-party tools: Service Connector Hub supports moving data to Oracle’s Kafka-compatible Streaming service so it's accessible from popular third-party tools using Kafka Connectors.
• Generate metrics from data and alarm on them: Service Connector Hub generates metrics from logs and ingests them to Monitoring from where alarms can be set up.
• Lightweight data processing with Functions: Service Connector Hub supports triggering Oracle Functions for lightweight data processing and building event-driven applications, enabling data engineers and developers to focus on the job to be done without the hassle of managing infrastructure.
• Get notifications about changes to your cloud resources: Service Connector Hub integrates with Notifications to send notifications as cloud resources change.
• Complete visibility over data movement: Service Connector Hub offers a central place where administrators can manage and monitor data movements across all their services instead of having to track point-to-point integrations across multiple services which can be error-prone.

The Logging service is a fully managed, highly scalable log management and search platform that simplifies collecting, managing, and exploring your logs. The service brings together your Oracle Cloud Infrastructure and application logs into one view. It lets you seamlessly ingest and manage the logs generated by your resources and applications. You can leverage the powerful log search engine to explore logs. Oracle’s new, intuitive rules engine makes every single. log line actionable in near real time. More details about the Logging service are available here.

Oracle Cloud Infrastructure Object Storage enables customers to store any type of data in its native format. This is ideal for building modern applications that require scale and flexibility, as it can be used to consolidate multiple data sources for analytics, backup, or archive purposes. More details about Object Storage are available here.

Oracle Cloud Infrastructure Streaming is a fully managed solution that enables applications to ingest large amounts of continuous data from multiple sources, making that data available for immediate processing. More details about Streaming are available here.

Oracle Cloud Infrastructure Monitoring provides your enterprise with fine-grained metrics and notifications to monitor your entire stack. Out-of-the-box performance and health metrics are provided for your Oracle Cloud Infrastructure resources. Additionally, alarms can be created on these metrics using industry standard statistics, trigger operators, and time intervals. Alarms alert you in real time to important changes across your cloud infrastructure and services via Notifications. You can also emit, visualize, and create alarms on your own custom metrics to monitor all of your metrics from one place. Monitoring offers a best-in-class metric engine, allowing you to perform powerful aggregation and slice-and-dice queries across multiple metric streams and dimensions in real time. More details about Monitoring are available here.

Oracle Functions is a functions-as-a-service offering on Oracle Cloud Infrastructure. It is a fully managed, multitenant, secure cloud service that makes it easy to build cloud native applications by letting developers focus on writing code and not on managing infrastructure. More details about Oracle Functions are available here.

Oracle Cloud Infrastructure Notifications is a fully managed, publish/subscribe service that pushes messages to a number of subscription endpoints at scale. Notifications supports delivering notifications via email delivery, Slack, PagerDuty, and custom HTTPS webhooks. More details about Notifications are available here.

Service Connector Hub is free. You only pay for the source and target services, such as Logging, Object Storage, Monitoring, Streaming, Functions, and Notifications, between which Service Connector Hub moves data.

You can access Service Connector Hub using the console (Service Connector Hub is under data and AI), REST API, command-line interface (CLI), or Terraform. Technical documentation for Service Connector Hub is available here.

A service connector defines the flow of data between a source and target service.

A source is a service that contains data that can be consumed by another service. Examples of source services include Logging and Streaming.

A target is a destination service which can either be a sink that is consuming data from a source, or an operator that is invoked at the end of a flow. Examples of targets are Object Storage, Streaming, and Functions.

Service Connector Hub currently supports Logging as a source and Object Storage, Streaming, Monitoring, Functions, and Notifications services as target services.

A task is a strongly typed unit of work that will be executed on the source data before it is delivered to the target service. For example, a logging query that filters data from the Logging Service.

The log task is expressed in Logging query language specification. To learn more, see documentation for Logging Query Language Specification.

See documentation for Logging Format Overview.

See Service Connector Hub API documentation.

Once created, service connectors run on a continuous basis to move data from a source to a target service.

See documentation for Service Connector Hub metrics.

Each service connector can move data from a single source to a single target.

Service Connector Hub supports a maximum of 5 service connectors per region (see documentation). For additional service connectors, please contact us to increase these limits.

Only authorized users can manage service connectors. To move data from a source, you must give your service connector the required authorization to write to the specified target resource in the target service. You can either accept the default policy offered when using the console to define the target service for a service connector, or make sure you have the proper authorizations in a group-based policy. For more information about service connector authorization, see Write Access to Target Services.

See documentation for Troubleshooting Service Connectors for the most common issues that you may face when using Service Connector Hub.