OT data

OT data

This is live, high frequency data commonly originating from a SCADA network. Timeseries have at least a timestamp and a value, but can also have metadata.

{
  "timestamp": "2024-06-12T09:00:00Z",
  "value": 100.0
}

Sending data to Digel

There are two ways to send timeseries data to Digel: via the HTTP API or via MQTT.

HTTP API

The simplest way to send timeseries data is via the HTTP API. You can send one or multiple data points in a single request.

curl --location 'https://<your-tenant>.digel.io/api/telemetry/ingest' \
--header 'apikey: <your-api-key>' \
--header 'Content-Type: application/json' \
--data '[
    {
        "timestamp": 1702900000000,
        "source": "production_line_1",
        "tag": "temperature",
        "value": 23.5
    },
    {
        "timestamp": 1702900000000,
        "source": "production_line_1",
        "tag": "pressure",
        "value": 1.2
    }
]'

Each data point requires:

• timestamp - Unix timestamp in milliseconds
• source - The source/device identifier
• tag - The measurement name
• value - The numeric value

MQTT

Digel also has a MQTT broker that you can send data into. Grab your token from the settings and send data to mqtt.digel.io:8883. This will automatically create the tags you need.

mosquitto_pub -d -q 1 -h mqtt.digel.io -p 8883 -t v1/devices/me/telemetry -u "<token>" -m "{temperature:25}"

Mapping data

You can change the mappings in the process canvas if something is not mapped correctly. We will try to automatically map tags to existing machines.