Deployment Monitoring

After installation, the deployment pages provide real-time visibility into the health and activity of your edge gateway. A deployment has five pages, reachable from its sidebar navigation: Overview, Configuration, Scope, Monitoring, and Telemetry.

Deployment statuses

The status updates automatically as the gateway progresses through its lifecycle.

Heartbeats

The Fleetera Edge Runtime on the gateway sends a heartbeat to the cloud every 60 seconds. Each heartbeat includes:

• Deployment ID — identifies the gateway
• VPN IP — the current private VPN address
• Runtime version — the version of the Edge Runtime running on the gateway
• Driver statuses — per-connector protocol driver health (connected, disconnected, or error), with reading and error counters
• Buffer metrics — store-and-forward buffer utilization, pending message count, and drain rate
• Host and container metrics — CPU, memory, disk, and per-container state
• Auto-update health — whether the Watchtower updater is running and whether the gateway can pull images from the registry

When a heartbeat is received, the deployment status is automatically set to Online. If no heartbeat arrives within five minutes, the status changes to Offline.

Overview page

The Overview page shows status tiles for Status, VPN IP, Last Heartbeat, Architecture, and Runtime (version), alongside the actions you use most:

• Install Command — the bootstrap command with the current token, and a Regenerate Token action when the token has expired or been used (available in Pending, Offline, or Error status)
• Decommission — starts the uninstall flow

Docker Compose card

The Overview page compares the compose file the gateway is actually running against what the platform would generate for it now:

When the compose is Stale, the card walks you through the fix: regenerate the compose, download it from the Configuration page, and re-apply it in the gateway's install directory (/opt/fleetera-edge/<alias> by default). Container images update automatically; the compose file itself is only ever replaced by you — the platform never modifies your host.

Auto-update health

The deployment page also surfaces the gateway's automatic-update health, built from two signals the runtime reports:

• Updater running — whether the Watchtower container is present and running on the host
• Image-pull health — the runtime periodically performs a lightweight registry probe (authentication and metadata fetch, no actual download) and reports OK, Failing, or Probe unavailable

See Troubleshooting for what to do when updates are not flowing.

Event log

The Overview page includes an event timeline that records key lifecycle events in reverse chronological order. Each entry shows a timestamp, event type, and a descriptive message.

Events are color-coded by severity — green for success events, amber for warnings like going offline, and red for errors. Heartbeat events appear in a muted style to keep the timeline readable.

Configuration page

The Configuration page holds the deployment's settings and the configuration sync surface:

• Deployment settings — site, architecture, alias / VPN hostname, and creation date
• The Auto-publish config toggle (see Auto-Publish)
• The store-and-forward buffer settings (hot buffer size, cold buffer size, retention)
• A Download Docker Compose button
• The Pending Changes and Config Sync cards (see Sync Status)

Scope page

Shows which part of the site's asset tree this gateway serves. By default a gateway serves the whole site; a scoped gateway only acquires data for the selected assets.

Monitoring page

The Monitoring page is the operational dashboard for the gateway:

• Gateway Health — status and heartbeat age, CPU / memory / disk gauges, connectivity chips, a resource trend chart, and a per-container table (status, CPU, memory, restarts)
• Edge Buffer Health — the store-and-forward buffer status: hot (memory) and cold (disk) buffer utilization, pending messages, drain rate, and whether the cloud data pipeline is reachable. A gateway in COLD mode is buffering to disk because it cannot deliver data — expect it to drain automatically once connectivity returns.
• Connector throughput — per-connector message and data-volume counters, with active asset and variable counts
• Ingestion throughput and signal health — charts of data arriving in the cloud from this gateway
• Recent events — the latest deployment events

A heartbeat less than a second old, or dated ahead of your device's clock, shows just now. Older heartbeats show their age in seconds, minutes, hours or days.

Telemetry page

Shows the live values flowing from this gateway's bound variables, so you can confirm end-to-end data flow after setup.