Skip to main content
Version: 8.3

Core Historian

Inductive University

Core Historian

Watch the video

This page lists the settings available when configuring a Core Historian, and provides an example of how to create one.

Settings​

Main​

PropertyDescription
NameSpecifies the unique name used to identify the historian provider.
DescriptionProvides an optional user-defined description for the provider.
EnabledSet whether this historian is enabled or disabled within the Gateway.
Partition IntervalGranularity of table partitioning (Week, Month, Year).
Data DeduplicationWhen enabled, incoming data with matching keys will update existing entries rather than creating new ones.

Maintenance​

PropertyDescription
ModeDetermines whether older data is archived to a target location or permanently deleted.
Maintenance AgeSpecifies the age threshold for data maintenance.
Maintenance Age UnitsSpecifies the time unit used for the data maintenance age threshold. Must be a whole number multiple of the Partition Interval, e.g., if the Partition Interval is DAY, the Maintenance Age must be a whole number of days (24 HOURS, 2 DAYS, 3 MONTHS, etc.)

Metadata Storage​

When enabled on a tag, metadata is stored automatically in system-managed tables. This includes properties like tag path, data type, units, and scaling. Metadata is preserved even if the tag is removed.

Metadata must be explicitly enabled in the Tag Editor by setting Include Metadata to true. This setting is found in the History section when editing a tag in the Designer.

Metadata is required for features like annotations, aggregates, and Historian scripting functions.

Configuring a Core Historian​

  1. Navigate to the Services > Historians > Historians section of the Gateway.

    Configuring a QuestDB Internal Historian Step 1

  2. On the Historians page, click Create Historian +.

  3. From the Create Historian form, select Core Historian, then click Next.

    Configuring a QuestDB Internal Historian Step 3

  4. Give your Historian an appropriate name, and configure the settings to align with your needs. In this example, we will name our Historian Core Historian, and leave the settings as the default. Click Create Historian when done.

    Configuring a QuestDB Internal Historian Step 4

Your Core Historian will now be listed and ready to store data.