...
- Type
- The type of History Store with options of In-Memory and Disk-Backed
- Data stored in an In-Memory History Store will not be persisted across a module configuration change, module disable/enable, module restart or power loss.
- Data stored in a Disk-Backed History Store will persist across a module configuration change, module disable/enable, module restart or power loss.
- Edge Node Tag Capacity
- Maximum number of Edge Node level tag change events to store per Edge Node before dropping oldest historical Edge Node tag change events. This value is independent of the 'Device Tag Capacity' and only applies to how many 'Edge Node level' tag change events are stored per Edge Node.
- Default 100,000
- A tag change event is triggered by either a change in value or quality and results in the tag's Qualified Value (which has three attributes of value, quality and timestamp) being stored.
- Device Tag Capacity
- Maximum number of Device tag change events to store per Device before dropping oldest historical Device tag change events. This value is independent of the 'Edge Node Tag Capacity' and only applies to how many 'Device level' tag change events are stored per Device.
- Default 10,000
- A tag change event is triggered by either a change in value or quality and results in the tag's Qualified Value (which has three attributes of value, quality and timestamp) being stored.
- Flush Quantity
- The maximum number of tags to publish in a single message upon reestablishing communication.
- Default 10,000
- Flush Period
- The period to wait in milliseconds between publishes when flushing messages upon reestablishing communication.
- Default 200
...
{"serverDuration": 181, "requestCorrelationId": "9ee0acab4b58282b"}