Ingestion to local Historian (Edge)

Local ingestion lets you persist measurements from selected tags to one or more historians running on the edge device.

---

Local Ingestion (Edge)

A prerequisite for implementing local ingestion is that one or more Historian Data Connectors are added to the Asset Hierarchy.

Currently the Historian Data Connector only supports the following database types:

• TimescaleDb: TimescaleDB is a PostgreSQL extension purpose-built for time-series and event data, designed for high-rate inserts and fast time-range queries, while leveraging the full SQL and the Postgres ecosystem.

When multiple historians are present, each Tag can be pointed to the specific historian you want. This gives you fine-grained control over where different datasets are stored locally.

Adding a Historian Data Connector at an Area enables local ingestion for every Tag beneath that Area in the Asset Hierarchy.

To add a historian connector, follow the setup steps in the Data Connectors documentation.

---

Configuring Tag

Once a Historian is configured, eligible Tags gain the option to store their measurements locally.

Shows the Store tab for a Tag, where local ingestion is enabled to a server called MyLocalHistorian.

The configuration needed is:

• Local Ingestion (Edge): This enables or disables the functionality to stored measurements to a local historian.

• Local Historian Upload Rate: Similarly to the Cold Path Upload Rate, this specifies how often data is uploaded to a local historian. If "Default" is selected, then the upload rate is set to the default value, as defined in the Data Connector settings.