Health Monitoring

Each connector in Fleetera tracks its current health status. This helps you identify connectivity issues and take corrective action before they affect data acquisition.

Health statuses

Status	Color	Description
Unknown	Gray	Health has not been checked yet. This is the initial state for new connectors.
Healthy	Green	The connector is functioning normally. Data is flowing as expected.
Degraded	Yellow	The connector is operational but experiencing issues — for example, intermittent timeouts, partial data, or elevated latency.
Offline	Red	The connector is not reachable or not responding. No data is being collected.

Where health is displayed

Connectors list — a colored badge on each connector row
Connector detail page — a status badge in the header and a health card in the overview showing the current status and last check timestamp
Asset connectors tab — protocol badge with health indicator

How health is determined

Health status is updated by external systems — typically the edge gateway or monitoring infrastructure — via the platform API. The status reflects the most recent health check result.

The edge gateway's config agent monitors connectivity to data sources and reports status changes back to the platform.

Troubleshooting

Status: Offline

The connector cannot reach the data source. Common causes:

Network connectivity — verify the edge gateway can reach the data source IP/hostname and port
Endpoint misconfiguration — check that the endpoint address is correct (e.g., opc.tcp://hostname:4840/path)
Firewall rules — ensure the required ports are open between the edge gateway and the data source
Data source down — verify the OPC UA server, Modbus device, or other data source is running

Status: Degraded

The connector is partially functional. Common causes:

Intermittent network — the connection drops and reconnects periodically
Timeout issues — the data source responds slowly, causing read timeouts
Partial access — some data points are accessible while others return errors (e.g., security permissions)
Resource constraints — the edge gateway or data source is under heavy load

Status: Unknown

Health has never been checked. This typically means:

The edge gateway has not yet started monitoring this connector
The deployment configuration has not been published to the edge
The edge gateway is offline

General troubleshooting steps

Check edge gateway status — verify the deployment is online in the Edge Gateway tab
Verify endpoint — confirm the connector endpoint is correct and accessible from the edge network
Check configuration sync — ensure the latest configuration has been published and applied
Review edge logs — check the config agent and edge device service logs on the edge gateway for error details
Test connectivity — for OPC UA connectors, use the OPC UA Discovery tool to test the connection independently

Health Monitoring

On this page