Difference between revisions of "Edge Data Service Configuration"
From Datonis
(→Maximum Number of In-Flight Messages) |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[Datonis Edge Gateway|Edge Gateway Home]] > '''Edge Data Service Configuration''' | [[Datonis Edge Gateway|Edge Gateway Home]] > '''Edge Data Service Configuration''' | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | == Auto | + | == Use HTTP Transport == |
| − | # | + | |
| − | # | + | # True for HTTP type communication. False for MQTT type communication. (Default will be False.) |
| − | # | + | |
| − | # | + | == Connect Auto on Startup == |
| − | + | ||
| − | + | # True for connecting automatically on edge restart or system startup. (Default will be True.) | |
| + | |||
| + | == Retry Interval == | ||
| + | |||
| + | # Data Connect retrial interval. (In Seconds. 0 to disable) | ||
| + | |||
| + | == Message Purge Age == | ||
| + | |||
| + | # Age in seconds of completed messages (either published with QoS = 0 or confirmed with QoS > 0) after which they are deleted (minimum 5). | ||
| + | |||
| + | == Message Store Capacity == | ||
| + | |||
| + | # Maximum number of messages persisted in the Data Store. The limit does not apply to messages with the priority less than 2. These priority levels are reserved to the framework which uses it for life-cycle messages - birth and death certificates - and replies to request/response flows. | ||
| + | |||
| + | == Message Store Size == | ||
| + | |||
| + | # Maximum number of messages in the store batch size that if exceeded triggers the batch persist. | ||
| + | |||
| + | == Maximum Period to Prioritize Latest Messages == | ||
| + | |||
| + | # Max period in seconds to determine latest messages. Messages older than the max period are considered stale and will be transmitted at a lower priority. To disable this feature mark this setting as 0 (Minimum period 300 seconds). | ||
| + | |||
| + | == Maximum Number of In-Flight Messages == | ||
| + | |||
| + | # The maximum number of in-flight messages. This should not be less than 'transmit.bulk-size' value. (The number of requests to be sent at a time.) | ||
| + | |||
| + | == Transmitting Messages Bulk Size == | ||
| + | |||
| + | # Max transmit bulk size limit (minimum 1). The number of messages per request. (Suppose 5 then a maximum of 5 messages will be sent in a single request.) | ||
| + | |||
| + | == Messages Bulk Splitting by Thing == | ||
| + | |||
| + | # Split bulk data message by thing to send transport requests per thing. (Thing 1s messages will be sent in 1st request then thing 2s and so on..) | ||
| + | |||
| + | == Data Disconnection Conditions == | ||
| + | |||
| + | # In case of Disconnectivity to the internet or the destination the data will be get stored in the local data store. After connecting again to the Internet or to the destination. The old Data will be sent 1st and then the latest. We can change the priority of message sending. | ||
| + | |||
| + | |||
__FORCETOC__ | __FORCETOC__ | ||
Latest revision as of 13:01, 14 January 2022
Edge Gateway Home > Edge Data Service Configuration
Contents
- 1 Use HTTP Transport
- 2 Connect Auto on Startup
- 3 Retry Interval
- 4 Message Purge Age
- 5 Message Store Capacity
- 6 Message Store Size
- 7 Maximum Period to Prioritize Latest Messages
- 8 Maximum Number of In-Flight Messages
- 9 Transmitting Messages Bulk Size
- 10 Messages Bulk Splitting by Thing
- 11 Data Disconnection Conditions
Use HTTP Transport
- True for HTTP type communication. False for MQTT type communication. (Default will be False.)
Connect Auto on Startup
- True for connecting automatically on edge restart or system startup. (Default will be True.)
Retry Interval
- Data Connect retrial interval. (In Seconds. 0 to disable)
Message Purge Age
- Age in seconds of completed messages (either published with QoS = 0 or confirmed with QoS > 0) after which they are deleted (minimum 5).
Message Store Capacity
- Maximum number of messages persisted in the Data Store. The limit does not apply to messages with the priority less than 2. These priority levels are reserved to the framework which uses it for life-cycle messages - birth and death certificates - and replies to request/response flows.
Message Store Size
- Maximum number of messages in the store batch size that if exceeded triggers the batch persist.
Maximum Period to Prioritize Latest Messages
- Max period in seconds to determine latest messages. Messages older than the max period are considered stale and will be transmitted at a lower priority. To disable this feature mark this setting as 0 (Minimum period 300 seconds).
Maximum Number of In-Flight Messages
- The maximum number of in-flight messages. This should not be less than 'transmit.bulk-size' value. (The number of requests to be sent at a time.)
Transmitting Messages Bulk Size
- Max transmit bulk size limit (minimum 1). The number of messages per request. (Suppose 5 then a maximum of 5 messages will be sent in a single request.)
Messages Bulk Splitting by Thing
- Split bulk data message by thing to send transport requests per thing. (Thing 1s messages will be sent in 1st request then thing 2s and so on..)
Data Disconnection Conditions
- In case of Disconnectivity to the internet or the destination the data will be get stored in the local data store. After connecting again to the Internet or to the destination. The old Data will be sent 1st and then the latest. We can change the priority of message sending.
