Contents
Cirrus Link Resources
Cirrus Link Website
Contact Us (Sales/Support)
Forum
Cirrus Link Modules Docs for Ignition 7.9.x
Inductive Resources
Ignition User Manual
Knowledge Base Articles
Inductive University
Forum
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 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
| Tip |
|---|
For ease of control we recommend setting a Primary Host ID in both MQTT Engine and in the MQTT Transmission. Removing the Primary Host ID from MQTT Engine will simulate the primary backend application going offline and cause MQTT Transmission to store data to the History Store. Restoring the Primary Host ID to MQTT Engine will simulate that the primary backend application is online and cause MQTT Transmission to flush the stored data. |
| Note |
|---|
The History Store values used in the video were selected to easily show the process for testing - it would be expected that a much higher Flush Quantity would be required in a live environment to . |
| Widget Connector | ||
|---|---|---|
|
...
Overview
Content Tools