Architecture

Monitoring that stays
outside the blast radius.

Equate keeps customer-network access on site. The cloud receives validated, durable telemetry and presents monitoring state without gaining a management path into the customer plane.

Read the technical overview
Customer OOB monitoring plane

Collect locally.

SNMPv2c devicesConfigured devices are independently polled.
SNMP CollectorNormalizes device, interface, health, and heartbeat observations.
SQLite outboxPersists telemetry before delivery and retains it during transport outages.
Local operator controlsUnix-socket TUI and status surfaces remain local only.
outbound-only
MQTT/TLS · QoS 1
→
UI/UX cloud plane

Understand centrally.

IngestionValidates routes and payloads, deduplicates, then persists transactionally.
PostgreSQLThe authoritative history and current monitoring state.
Read-only APIShapes monitoring evidence for frontend clients.
DashboardShows sites, devices, interfaces, history, and health evidence.
Reliable delivery

Observe first. Deliver safely.

MQTT is a delivery boundary, not the system of record. The collector continues polling when cloud transport is unavailable.

01 · collector

Enqueue before publish

Poll→SQLite outbox→MQTT/TLS

The collector removes buffered telemetry only after broker acknowledgement.

02 · ingestion

Commit before acknowledge

Validate→Deduplicate→Commit

Database failure leaves a message unacknowledged so QoS 1 delivery can retry safely.

03 · dashboard

Present persisted evidence

PostgreSQL→API→Dashboard

The dashboard reads API projections; it does not query devices, collectors, or the database directly.

Health evidence

Make impact visible without guessing.

Health is evaluated where the collector can observe polling results and configured dependencies. The dashboard preserves that evidence rather than recomputing it.

Healthy

The device responded and its temperature is below the active threshold.

Warning

The device responded, but temperature is at or above its collector policy threshold.

Critical

The device is directly unreachable after the configured consecutive-failure threshold.

Unknown impact

All configured upstream paths are unavailable. This is dependency evidence, not a claim that the device itself has failed.

Plan the monitoring path.

Review collector placement, inventory, outbound connectivity, and dashboard requirements before rollout.

Talk to the team