Connector Hub FAQ

FAQ topics

General questions

What is Oracle Cloud Infrastructure (OCI) Connector Hub?

Oracle Connector Hub is a free service that provides a single pane of glass for describing, executing, and monitoring data movements between all your services—within Oracle Cloud Infrastructure and from Oracle Cloud Infrastructure to third-party tools. It helps move data to sink services, such as Oracle’s Logging, Object Storage, Streaming, and Monitoring, by providing out-of-the-box integrations. It can also trigger Functions for lightweight data processing and send Notifications about changes to your infrastructure.

What can I do with Connector Hub?

Common use cases include:

  • Cheap, long-term data archival: Connector Hub integrates with Object Storage to move data for cheap, long-term archival.
  • Integrate with third-party tools: Connector Hub supports moving data to Oracle’s Kafka-compatible Streaming service so it's accessible from popular third-party tools using Kafka Connectors.
  • Run advanced log analytics: Connector Hub moves logs to Logging Analytics to support monitoring, aggregating, indexing, and analyzing all log data in the Logging service.
  • Generate metrics from data and alarm on them: Connector Hub generates metrics from logs and ingests them to Monitoring from where alarms can be set up.
  • Lightweight data processing with Functions: 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: Connector Hub integrates with Notifications to send notifications as cloud resources change.
  • Complete visibility over data movement: 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.

What is the Logging service?

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.

What is Object Storage?

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.

What is the Streaming service?

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.

What is Logging Analytics?

Oracle Cloud Infrastructure Logging Analytics is a machine-learning–based cloud service that monitors, aggregates, indexes, and analyzes all log data from on-premises and multicloud environments. It enables users to search, explore, and correlate this data to troubleshoot and resolve problems faster and derive insights to make better operational decisions.

What is the Monitoring service?

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.

What are Oracle Functions?

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.

What is the Notifications service?

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.

What is the pricing for Connector Hub?

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 Connector Hub moves data.

How do I get started with Connector Hub?

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

What is a connector?

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

What is a source?

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

What is a target?

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.

What Source and Target services are currently supported?

Today, the Connector Hub supports Logging and Streaming as a Source and Object Storage, Streaming, Logging Analytics, Monitoring, Functions, and Notifications services as Target services.

What is a task?

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. Examples include:

  • A logging query that filters data from the Logging Service.
  • A Function configured to process data in motion before it’s written to a target.

What is syntax of a log task?

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

What is the format of a log?

See documentation for Logging Format Overview.

What are the available API operations for Connector Hub, and where can I find documentation?

See Connector Hub API documentation.

How often do connectors move data?

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

What metrics can I use to monitor Connector Hub?

See documentation for Connector Hub metrics.

How many target services can a single connector move data to?

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

What are the service limits for Connector hub?

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

Who can create connectors?

Only authorized users can manage connectors. To move data from a source, you must give your 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 connector, or make sure you have the proper authorizations in a group-based policy. For more information about connector authorization, see Write Access to Target Services.

How can I troubleshoot issues with Connector Hub?

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