SpecsModelExplore
Overview
Actors
External Systems
IoT Platform
Edge
Edge Agent
Driver LoaderLocal BufferMQTT PublisherOTA Updater
Edge Rule Runtime
Ingestion
Stream Processing
Device Management
User-Facing Apps
Platform
SpecsModelExplore
Edge Agent
OverviewGuideLinks and Communications
IDproduct.edge.edge_agent
DescriptionContainerized agent running on local gateways.
Keyedge_agent
Typemicroservice:service
TeamEdge Platform
Owneredge-platform@iotgateway.example
Statusactive
TechnologiesRust, MQTT, SQLite, Protobuf
Attributesfootprint: 48MB, language: Rust, runtime: container
Tags
Table of contents
Guide
Edge Agent
Internal structure
Components
The data path
Buffer
Publish
Update channel
Related workflows

Guide

Edge Agent

The Edge Agent is the workhorse process on every gateway. It loads the device drivers, pulls readings off the local bus, persists them durably so nothing is lost during a network blip, and streams them up to cloud ingestion over MQTT. It is also the channel through which firmware and config updates land on the box.

Store-and-forward by default

The agent never assumes the network is up. Every reading is written to the Local Buffer first, then published. On reconnect the backlog drains in order — at-least-once, oldest-first.

Internal structure

Could not build diagram for model "example-iot".

Components

Driver Loader

Loads and supervises the per-device-type driver plugins.

Local Buffer

On-device SQLite store that holds telemetry and outbound commands.

MQTT Publisher

Drains the buffer and publishes to the cloud broker over TLS.

OTA Updater

Verifies and applies signed firmware / config updates.

The data path

Collect

The Driver Loader polls each attached device through its driver and normalises the readings into the internal Protobuf message shape.

Buffer

Readings are appended to the Local Buffer. This is the durability boundary: once a reading is committed here, it will be delivered even across a reboot.

Publish

The MQTT Publisher reads committed batches, ships them to the cloud, and only then advances the sync cursor so acknowledged data can be pruned.

Update channel

Firmware and config never push directly onto the device. The cloud announces an update; the OTA Updater downloads, verifies the signature, and applies it with an A/B rollback safety net.

Related workflows

Telemetry collected here is the start of the alert pipeline:

Cloud commands are received and acted on by the agent:

Firmware rollouts terminate at the agent’s OTA updater:

Links and Communications

3 workflows

Related Workflows(3)

WorkflowModelParticipant idParticipant label
Command dispatch

commands.dispatch

example-iotproduct.edge.edge_agentEdge agent
OTA firmware rollout

device-lifecycle.ota-rollout

example-iotproduct.edge.edge_agentEdge agent
Telemetry to alert

telemetry.alert-pipeline

example-iotproduct.edge.edge_agentEdge agent