Data Ingestion (Southbound)
Overview of southbound data ingestion in AnyLog — connectors, mapping, file pipeline, and prerequisites.
AnyLog receives data from edge devices, sensors, and applications through a set of southbound connectors. All connectors ultimately produce JSON files that flow through a common pipeline: Watch Directory → Operator → Local Database.
This page covers the pipeline, prerequisites, and mapping. For connector-specific configuration see the individual pages linked below.
See also: Northbound Interfaces (data egress) — the counterpart to this page, covering how AnyLog forwards data onward once it’s ingested and stored.
The ingestion pipeline
Data Source
│
▼
Southbound Connector
(MQTT, REST PUT, Kafka, gRPC, PLC/OPC-UA, Syslog, ...)
│
▼
Internal Buffers / Streamer
(aggregates events, flushes on time or volume threshold)
│
▼
Watch Directory (JSON files)
│
▼
Operator
(reads files, maps JSON → SQL, inserts to local DB)
│
▼
Local Database (SQLite / PostgreSQL)
The connectors
Built-in Southbound connectors
- REST
- PUT — data is stored as-is.
- POST — requires a message client to translate the payload before it’s stored.
- MQTT / Kafka — utilizes AnyLog’s built-in MQTT / Kafka message broker.
- OPC-UA
- Modbus
- DNP3
- EtherIP
- gRPC
- Video
Third-Party Southbound Connectors
AnyLog focuses on the data management side rather than pulling data directly from every device and protocol. Where we don’t have a built-in connector, we recommend placing a third-party app between the device and AnyLog to bridge the gap — the app talks to the device/sensor, and forwards the result to AnyLog over REST, MQTT, or Kafka.
Node Monitoring
Node and container health metrics (CPU, memory, disk, container status) are themselves ingested through this same southbound pipeline — which is why monitoring configuration lives here rather than under Extended Services.
Dummy Data
We provide an MQTT connection to an array of different data sets. For details visit Data Ingestion or Live Data Generator to run locally.