> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.2/connectors/introduction-to-connectors/bridge.md).

# Bridge

The Bridge component establishes a secure connection between cloud-hosted platforms and customer-hosted data sources. To initiate connectivity, deploy the Bridge Client within the customer infrastructure. Whitelist the relevant IP addresses and ports of the target data sources. This configuration allows secure access without requiring changes to firewall rules.

## Manage Bridge

1. Log into the application.
2. Navigate to **Administration** >  **Connectors**.
3. Click **Manage Bridge** to open the Bridge interface.

   <figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeQYdA7lnoUo3e_aJ4loW2bbj8OsrRpVfEL0JBp0kyRYjl5esJCIsdeL6Sf_bvbwvJ6--y99qZnnQs6V5_1Du7c51wx9fwCVUnDlOPw_w635Ya9qu3sEoRHrhwU5c0L7Yy1bhrlyw?key=kU5fqtI4eAzquyCyuBsp-g" alt=""><figcaption></figcaption></figure>

The interface lists all configured bridges with key operational and configuration details, including:

* **Bridge ID**: Unique identifier assigned to each bridge instance
* **Bridge Name**: Descriptive name defined during setup
* **IP Address**: Network address of the Bridge Client host
* **Port**: Designated communication port used by the client
* **Status**: Current state of the bridge (Running, Stopped, etc.)
* **Type**: Defines the category of the bridge.
* **Registration Date**: Date when the bridge was registered in the system
* **Created By**: User account that created the bridge instance
* **Action**: Provides control options for each bridge. It includes the following icons:
  * **Restart Bridge**: It allows the bridge client to re-establish connectivity without reinstalling.
  * **Update Bridge:** Updates the bridge client with the latest available software version.
  * **Delete Bridge**: Removes an unused bridge from the application. Available only to OE\_ADMIN users for inactive, disconnected, or failed bridges. The system validates that the bridge is not in use before deletion. Active or running bridges cannot be deleted.
* **Version**: Current version of the bridge software
* **Statistics**: Provides a shortcut to view runtime performance, technical metrics, data flow, and server activity
* **Last Updated On:** Timestamp of the most recent configuration or status update
* **Last Updated By:** User who performed the last modification
* **Action Status**: Outcome of the most recent operation.<br>

  <figure><img src="/files/2hwZBWJM1Z0Dq9XQnvOa" alt=""><figcaption></figcaption></figure>

### Bridge Status

The Bridge Status feature provides real-time visibility into the operational health of a bridge. Bridge status is continuously monitored using heartbeat signals and system events, enabling administrators to quickly identify connectivity issues, maintenance activities, and recovery events.

Each bridge displays a Status and a Mode that together indicate the current operational state and how the state was triggered.

<div align="left"><img src="/files/clLKvxuPkn6N2swKQ6cQ" alt="" height="289" width="624"></div>

#### Bridge Modes

Bridge modes identify the source of a status change.

<table><thead><tr><th width="145">Mode</th><th>Description</th></tr></thead><tbody><tr><td>Auto (User)</td><td>Indicates that the operation was initiated by a user from the OvalEdge application, such as restarting or updating a bridge.</td></tr><tr><td>Auto (System)</td><td>Indicates that the operation or status transition was triggered automatically by the system, such as heartbeat monitoring or scheduled operations.</td></tr><tr><td>Manual</td><td>Indicates that the bridge state changed because of an external action outside the OvalEdge application, such as an operating system restart or manual intervention.</td></tr></tbody></table>

#### Bridge Statuses

The following statuses indicate the current operational state of a bridge.

<table><thead><tr><th width="151">Status</th><th>Description</th></tr></thead><tbody><tr><td>Running</td><td>The bridge is operational and communicating successfully with the application.</td></tr><tr><td>Warning</td><td>Heartbeat communication is delayed, indicating a potential connectivity issue.</td></tr><tr><td>Stopped</td><td>The bridge is unavailable because heartbeat communication has stopped.</td></tr><tr><td>Restarting</td><td>A bridge restart operation is currently in progress. The application restarts the Bridge and waits for a healthy heartbeat.</td></tr><tr><td>Updating</td><td>A bridge update is in progress and the bridge will restart after the update completes.</td></tr><tr><td>Inactive</td><td>The bridge has been registered but is not yet validated or has not established communication with the application.</td></tr></tbody></table>

#### Heartbeat Monitoring

The application checks the health of every Bridge every 1 minute by validating the latest heartbeat received from the Bridge. The application automatically updates the bridge status based on the most recent heartbeat received.

<table><thead><tr><th width="153">Bridge Status</th><th>Heartbeat Condition</th></tr></thead><tbody><tr><td>Running</td><td>The application receives a heartbeat within the last 5 minutes.</td></tr><tr><td>Warning</td><td>The application does not receive a heartbeat for 5 to 10 minutes. This status indicates a potential connectivity issue or a temporary interruption.</td></tr><tr><td>Stopped</td><td>The application does not receive a heartbeat for more than 10 minutes. This status indicates that the Bridge is unavailable.</td></tr><tr><td>Recovery</td><td>The application changes the Bridge status back to Running after it receives a new heartbeat from a Bridge in the Warning or Stopped state.</td></tr></tbody></table>

The application applies the same heartbeat thresholds after a Bridge restart or update. If the application does not receive a healthy heartbeat within 10 minutes, it marks the operation as failed and changes the Bridge status to Stopped.

The application records every Bridge status change and health event to support operational monitoring and troubleshooting. Alert generation follows configured thresholds to reduce unnecessary notifications during temporary connectivity fluctuations.

#### Bridge Operations

During bridge maintenance operations, the application automatically updates the bridge status to reflect the current activity.

* Restart operations display the Restarting status until the application receives a healthy heartbeat.
* Update operations display the Updating status until the update completes successfully and the application receives a healthy heartbeat.
* If the application does not receive a healthy heartbeat within 10 minutes after a restart or update operation, it changes the Bridge status to Stopped and records the operation as failed to assist with troubleshooting.

#### Bridge Failure Handling

The application detects failures that occur during Bridge operations, such as update, deployment, NAR download, and NAR deployment failures. The application updates the Bridge status with the appropriate failure state and displays relevant error information. This enables administrators to quickly identify failed operations, determine the stage at which the failure occurred, and take corrective action.

**Steps**

1. Click the **Status icon** to view the current state of each bridge.
2. A detailed status pop-up appears after clicking the **Status** icon. The pop-up includes the following parameters:
   1. **Bridge Health:** Real-time condition of the bridge (e.g., Running, Stopped, Restarting, Warning)
   2. **Details**: Contextual information (e.g., “Manually restarted”)
   3. **Mode**: Configuration mode, either Auto or Manual
   4. **Last Health Check Timestamp:** Date and time of the most recent health verification

      <figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfp85sM9tkLNIzgExr8pjnOOx9vrJvBUZy-wC4lHnkpZPau0xMs00UkgBzNijFnppudV3tfGlFzOGOLl0_eFYWzDQhGnvo81Ku5z0uaMha_BjBPlj86N94_TdkvHPV2ihS5QH7B8Q?key=kU5fqtI4eAzquyCyuBsp-g" alt=""><figcaption></figcaption></figure>

### **Automated Notification**

When the application does not receive a heartbeat for 5 to 10 minutes, it changes the Bridge status to Warning. When the application does not receive a heartbeat for more than 10 minutes, it changes the Bridge status to Stopped and automatically generates a health notification.

During Bridge downtime, the application captures the list of currently running Bridge jobs to help Integration Admins identify workloads that may have been affected. The application sends notifications to the configured recipients or notification channels to help Integration Admins monitor and manage Bridge operations.

#### Bridge Health Event Notifications

The application monitors Bridge resource utilization and generates health notifications when the defined monitoring conditions are met. The application sends notifications to the configured recipients or notification channels to help Integration Admins monitor Bridge health and respond to operational issues.

The application generates Bridge health event notifications for the following events.

<table><thead><tr><th width="220">Event</th><th>Description</th></tr></thead><tbody><tr><td>Physical Memory Critical</td><td>Generated when the available physical memory falls below the configured threshold.</td></tr><tr><td>Non-Heap Memory Alert</td><td>Generated when non-heap memory usage exceeds the configured threshold.</td></tr><tr><td>Heap Memory Warning</td><td>Generated when heap memory usage exceeds the configured warning threshold.</td></tr><tr><td>Process CPU Alert</td><td>Generated when Bridge CPU utilization exceeds the configured threshold.</td></tr></tbody></table>

### Bridge Statistics

1. Click the **Statistics** icon to access a detailed Statistics interface: **Release Info**.

<figure><img src="/files/CBVS8jtoHpu4DwtNTo7Q" alt=""><figcaption></figcaption></figure>

#### **Release Info Tab**

The Release Info tab provides build, release, and component version details of the Bridge. The information helps validate the deployed bridge version and assists with auditing and troubleshooting activities.

This tab displays the following details:

* **Bridge ID**: Unique identifier of the bridge instance.
* **Bridge Branch**: Source code branch used for the build.
* **Commit**: Short commit ID associated with the build.
* **Commit Full**: Full commit hash for detailed traceability.
* **Tag**: Release tag mapped to the build.
* **Release**: Name of the release.
* **Release Number**: Numeric identifier of the release.
* **Release Version**: Version number of the bridge release.
* **Bridge Components**: Displays version information for the Bridge components and associated libraries included in the release.
* **NiFi Version**: Version of Apache NiFi used by the bridge.
* **Java Version**: Java version used to run the bridge.
* **OS Name**: Operating system on which the bridge is running.
* **Build Date**: Date and time when the bridge build was created.

<figure><img src="/files/LMi6ifFXPESWIITIGmwO" alt=""><figcaption></figcaption></figure>

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners GA USA


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ovaledge.com/release8.2/connectors/introduction-to-connectors/bridge.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.