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. If configured latency information will be added to two other fields, describing the time elapsed since the initial timestamp. Each entry has a corresponding event entry.

For example:

Field	Value
LTY_INIT_TS	1125062541880
LTY_LIST_EVENT	datasrc1_E,datasrc1_X,transformer1_E,transformer1_X,rttpd1_E,rttpd1_X
LTY_LIST_TS	0,1,3,4,5,8

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:

Event	Value	Meaning
datasrc1_E	0	Time elapsed between inital timestamp and entering datasrc1
datasrc1_X	1	Time elapsed between inital timestamp and exiting datasrc1
transformer1_E	3	Time elapsed between inital timestamp and entering transformer1
transformer1_X	4	Time elapsed between inital timestamp and exiting transformer1
rttpd1_E	5	Time elapsed between inital timestamp and entering rttpd1
rttpd1_X	8	Time elapsed between inital timestamp and exiting rttpd1

`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