Configuring History

Before we get started on the requirements for enabling History on MQTT Engine Tags, one should take note of the two ways that MQTT Engine historical event processing can result in historical inserts into the database:

...

1. History must be enabled on the Edge via Transmission side configuration settings.
1. A History Store must be defined under MQTT Transmission -> History -> History Stores and it must be enabled.
2. A Transmitter under MQTT Transmission -> Settings -> Transmitters must consume the enabled History Store.
3. Ignition 8 Only: “Enable History Storage by Default” needs to be enabled or the 'CL Store Forward Enabled' custom property must exist on the Edge side Tag in order for historical events to be sent to MQTT Engine.
   
   
2. History *must* be enabled on the MQTT Engine Tag and the history settings for that Tag must be as follows:
1. History Enabled: true
2. Storage Provider: Must be set to an existing Storage Provider
3. Sample Mode: On Change
4. Min Time Between Samples:  0 ms
5. Ignition 7 Only: “Timestamp Source” must be set to “Value” (*not* “System”)
   This is required in order for the historical event to have the timestamp when the value changed on the Edge, instead of when the historical event is being processed by Engine. Having the “Timestamp Source” set to “System” will result in historical events being inserted with the wrong (later) timestamp.
   NOTE: the above history settings will ensure the proper historical event processing by MQTT Engine when writing history directly to the database and when writing history directly to the Tag.

History Stores Metrics & Flushing History

One can determine the current size of the History Store by examining the History Store metric tags under [MQTT Transmission]Transmission Info/History Store. These tags will show the number of historical metrics stored per edgenode/device and how much memory/disk is being consumed by these metrics. These tags update live (count down) as historical data is flushed. 

Image Added