Recording and playing back message received timestamp in rmdstestclient and sink_driven_src tool
Is there a way for us to configure the rmdstestclient to also record the timestamp at which each message was received and then have the sink_driven_src put that timestamp in a separate FID of the message during playback? This would allow us to more accurately simulate exactly what happens when consuming the data in a live production setting.
Best Answer
-
For rmdstestclient, you may try using option -m and -micro to log the message timestamp.
Here there are the descriptions:
-? print help (False)
-S Service Name or Comma Separated Services List. Max 10 Services can be specified. Format serviceName@connectionType@SvrHostname@sipcVersion
-f Item List File
...
-m Prepend timestamp (milliseconds) (False)
-micro Prepend timestamp (microseconds) (False)
...For example,
rmdstestclient -h 192.168.27.46 -S API_ELEKTRON_EPD_RSSL -u rmds -f items.txt -X -V -a
And this is another example for adding -m and -micro to running arguments:
rmdstestclient -h 192.168.27.46 -S API_ELEKTRON_EPD_RSSL -u rmds -f items.txt -X -V -a -m -micro
The time values are timestamp when rmdstestclient receives messages.
Hope this helps.
0
Answers
-
Understood. Is there a way to include these timestamps in the message (either in a separate FID in the message) when sink_driven_src plays back the data? Ideally I want the client receiving the playback message to be able to figure out exactly what time the message was recorded.
0 -
No, sink_driven_src uses "capture" file to replay data, while the received timestamps are recorded into "log" file.
For end-to-end latency measurement, you may find useful the performance tools that are included within Elektron SDK, EMA->Examples->PerfTools, complete with the source code
0 -
Got it. Is there anyway for us to get the source code to rmdstestclient and sink_driven_src so that we can make custom modifications to it?
0 -
Both rmdstestclient and sink_driven_source are part of infrastructure tools, not developer kits, so no, the source code is not available.
To simulate exactly what happens in production, in terms of time received, you may wish to talk to your Account team about a product called ReplayService
0
Categories
- All Categories
- 6 AHS
- 37 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
- 367 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
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛