Page History

...

• Configure a History Store with large Edge Node Tag Capacity and Device Tag Capacity
• Disconnect for a set time period
• Monitor the live updates for the count of tag change events and memory used from the Transmission Info History Store metrics

• Reconnect and monitor the data flushing to ensure that the Flush settings (quantity and period) are able to handle the current tag changes that continue to build.

  Warning
  icon false
  Whilst the history flush is in progress, all new change events are written to the history store until it has been completely flushed. If the tag change rate at the Edge is faster than the MQTT Transmission Flush Period this can cause a build up of data in history store(s) and prevent the publishing of live data.

  
  

• Extrapolate based on the test  

...