# Ingestion

> Write high-volume timestamped telemetry into Infuse-DB.

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 Cloud 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.

<table>
<thead>
  <tr>
    <th>
      Record type
    </th>
    
    <th>
      Use
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Raw telemetry
    </td>
    
    <td>
      Source readings, status, events, or operational signals from devices and gateways.
    </td>
  </tr>
  
  <tr>
    <td>
      Computed data
    </td>
    
    <td>
      Derived values, summaries, enriched records, or application-ready signals.
    </td>
  </tr>
</tbody>
</table>

Use raw records when teams need traceability back to device output. Use computed records when downstream systems need stable, queryable operational signals.

## Infuse-IoT Cloud Alignment

Keep Infuse-DB records aligned with Infuse-IoT Cloud by carrying identifiers and context through ingestion:

<table>
<thead>
  <tr>
    <th>
      Field
    </th>
    
    <th>
      Why it matters
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <code>
        deviceId
      </code>
    </td>
    
    <td>
      Links stored records to the Infuse-IoT Cloud device registry.
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        organisationId
      </code>
    </td>
    
    <td>
      Preserves account ownership.
    </td>
  </tr>
  
  <tr>
    <td>
      Board or hardware profile
    </td>
    
    <td>
      Supports hardware-level analysis.
    </td>
  </tr>
  
  <tr>
    <td>
      Definition version
    </td>
    
    <td>
      Makes decoded telemetry reproducible.
    </td>
  </tr>
  
  <tr>
    <td>
      Event timestamp
    </td>
    
    <td>
      Supports live and historical time-series queries.
    </td>
  </tr>
</tbody>
</table>

For a cross-product workflow, see [Stream IoT Data to Infuse-DB](/guides/data/stream-iot-data-to-infuse-db).