Fivetran HVR

Fivetran HVR is a real-time Change Data Capture (CDC) replication platform that moves data between source and target systems in near real-time using a hub-and-channel model. This integration connects ADOC to your HVR Hub Server and automatically surfaces every replication channel as a monitored pipeline in Pipeline Observability, alongside your other pipeline types.

With this integration, you can:

• Monitor channel health status (Running, Suspended, Error, Latency Exceeded, Stopped, or Initializing) in real time

• Track capture latency, integrate latency, and throughput metrics per channel

• Surface HVR failure events as pipeline alerts, routable through your existing notification channels

• View source-to-target asset lineage for replicated tables, including many-to-one and one-to-many topologies

Prerequisites

• Fivetran HVR version 6. Earlier HVR versions are not supported.

• An HVR Hub Server accessible from the Acceldata Data Plane on the configured port (default: 4340).

• Valid HVR credentials with permission to query hub and channel APIs.

Add Fivetran HVR as a Data Source

1. Navigate to Control Center > Integrations and click Add Data Source.

2. Select HVR as the data source type.

3. Enter the HVR Hub URL (for example, http://<hvr-host>:4340), Username, and Password.

4. Click Test Connection. ADOC authenticates with the Hub Server and retrieves the available hubs.

5. From the HVR Hubs selector, choose one or more hubs to monitor.

6. Optionally configure the Polling Interval. The default is 60 seconds.

7. Click Save. ADOC begins discovering channels and registering them as pipelines.

Note Multiple hubs can be added from a single Hub Server. Each hub is monitored independently.

View Pipelines and Metrics

• Pipeline list — Navigate to Pipelines in the left navigation. HVR channels appear as individual pipeline entries. Use the Datasource filter to scope the view to a specific HVR data source.

• Pipeline detail — Click any HVR pipeline to view current status, latency metrics, throughput statistics, failure events, and the lineage graph.

• Lineage graph — The lineage view shows all source and target tables for the channel, including many-to-one and one-to-many replication topologies.

How Monitoring Works

ADOC uses two polling cycles to keep channel data current. A tick runs every 60 seconds to identify channels whose metadata was last synced 15 minutes or more ago. For each of those channels, a full channel sync is performed, collecting current status, latency and throughput statistics, and any active alerts. The combined effect is that each channel's metadata is refreshed approximately every 15 minutes.

When a channel or data source is deleted in ADOC, the associated pipeline and its history are removed. If a channel is deleted in HVR itself, the pipeline transitions to a stopped state on the next tick.

Supported Configurations

Notes and Limitations

• Polling-based monitoring means there may be a short lag between an event occurring in HVR and it appearing in ADOC.

• Per-job span event granularity within individual HVR job executions is not yet fully implemented and is planned for a subsequent release.

• The datasource filter in the pipeline list has been validated for single-datasource configurations. Behavior with a large number of concurrent HVR datasources should be validated in your environment.