The following options are to setup this DataSource component to add latency information to each update. For this to work the update must already have an initial timestamp in milliseconds on a particular field or the config option latency-chain-auto-seed set to true. If configured and an initial timestamp is present latency information will be added to two other fields, describing the time elapsed since the initial timestamp. Each entry has a corresponding event entry. In the case where there is no initial timestamp present on the record and latency-chain-auto-seed is enabled, the first add will add an intitial timestamp rather than latency deltas.

For example:

The comma seperated list of deltas correspond to the event names in the list of events. Each value represents the milliseconds since the initial timestamp that the event occured. For each component there should be a Enter (E) and an Exit (X) event. Note that in some cases Liberator will not add an Exit event, such as when the message is a cached value and the Exit time would be very large.

The above value break down to the following information:

latency-chain-enable

Type: Boolean
Default: FALSE

Enable Latency Chaining

latency-chain-name

Type: String
Default: %a

Latency Chain Name used for event list field

latency-chain-init-ts-field

Type: String
Default: LTY_INIT_TS

Latency Chain Init Timestamp Field Name

latency-chain-list-event-field

Type: String
Default: LTY_LIST_EVENT

Latency Chain Event List Field Name

latency-chain-list-ts-field

Type: String
Default: LTY_LIST_TS

Latency Chain Timestamp List Field Name

latency-chain-auto-seed

Type: Boolean
Default: FALSE

Automatically seed the latency chain when sending dsdata without latency chain information