Accessing provider generated timestamps and the role of \Control\MessagePools\OMMItemEventPool\enabl
Hi
I'm sourcing level I (top of book) data from TREP and would like to know the timestamp of the market event that led to each update I receive from TREP. How can I access this provider generated timestamp?
On the event data structure in the .NET api, each ThomsonReuters.RFA.Common.Event has an EventAge property, enabled by the config key
\Control\MessagePools\OMMItemEventPool\enableOMMEventAge
However, this property is often 0 or lower than what I'd expect from network transit delays.
How is the EventAge property defined, and how do I access the provider generated event timestamps?
Sincerely
Anders A. Søndergaard
Best Answer
-
RFA does not provide the time stamp you mentioned. Event in this case is RFA internal event/message. The Event Age is the number of milliseconds since RFA created the Event. The method will return -1 if enableOMMEventAge configuration parameter is false. To enable the functionality, enableOMMEventAge need to be set to true.
The amount of time returned from the getEventAge method is the time difference between the time when the event is received from the connection and the time when the application calls the method (both at the receiver side). This means the event age is measured from the moment the event is created at the receiver side (e.g. a consumer) rather than the time when the event is created on the sender side (e.g. a provider/TREP). Please note that the enableOMMEventAge parameter of a RSSL connection must be set to true to enable this feature; otherwise, -1 is returned from the methods.
0
Answers
-
I think I found a partial answer here
Does the naming of the timestamp field depend on the provider?
I still don't understand the purpose of EventAge.
0 -
Thanks a lot for the clarification.
I'll assume that the naming of the timestamp fields is provider specific and mark your question as the accepted answer.
0 -
The timestamp mentioned in the post is one of the fields provided by the data feed. So it depends on Exchange or Provider to use the field or it may use another field to provide the time stamp.
0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 370 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛