Ingestion
Ingestion workflows write timestamped records into Infuse DB from devices, gateways, backend services, jobs, or integrations.
For IoT products, ingestion usually starts with data emitted by devices and interpreted with Infuse IoT context. Your ingestion path should preserve the device identity, event time, and dimensions needed for later filtering.
Ingestion Responsibilities
Before writing production records, your ingestion service should:
- validate the device identity,
- normalize timestamps,
- attach dataset dimensions such as customer, environment, location, or asset group,
- preserve raw telemetry where it is needed for audit or troubleshooting,
- compute derived signals where applications need higher-value records,
- separate production and non-production data.
Raw And Computed Records
Infuse DB is intended to hold both raw and computed device streams.
| Record type | Use |
|---|---|
| Raw telemetry | Source readings, status, events, or operational signals from devices and gateways. |
| Computed data | Derived values, summaries, enriched records, or application-ready signals. |
Use raw records when teams need traceability back to device output. Use computed records when downstream systems need stable, queryable operational signals.
Infuse IoT Alignment
Keep Infuse DB records aligned with Infuse IoT by carrying identifiers and context through ingestion:
| Field | Why it matters |
|---|---|
deviceId | Links stored records to the Infuse IoT device registry. |
organisationId | Preserves account ownership. |
| Board or hardware profile | Supports hardware-level analysis. |
| Definition version | Makes decoded telemetry reproducible. |
| Event timestamp | Supports live and historical time-series queries. |
For a cross-product workflow, see Stream IoT Data to Infuse DB.