monitoring data updates
Hi,
Our system subscribes to most global markets via ERT. While monitoring at service "IDN" level is setup, data updates may stop for a particular exchange even though IDN status is Up. How can data monitoring be implemented for accurate real-time feed status check? One way would be to configure monitoring system to capture SALTIM & TRDPRC_1 fields and if no updates after a configurable interval, it probably indicates updates are stopped for a particular ric.
Are there other ways to monitor data updates?
Thank you
Best Answer
-
The legacy MarketFeed format is slightly different.
The legacy MarketFeed status uses a single enum variable, State.
enum State {
/// The data contained within the event is OK
Ok = 1,
/// The data contained within the event is stale.
/// It may not be consistent with the data source.
Stale = 2,
/// The data stream for this item has been closed.
Closed = 3,
/// The data stream for this item has been closed.
/// The application may be able to recover this item.
ClosedRecover = 4,
/// There is no change from the previous state.
NoChange = 5
};The application can get the data state by calling getStatus().getState().
const rfa::sessionLayer::MarketDataItemEvent & MDEvent =
static_cast<const rfa::sessionLayer::MarketDataItemEvent&>(event);
MarketDataItemStatus::State state = MDEvent.getStatus().getState();But overall concept is still the same. No update doesn't equal to data status down. If data status down, you should receive "Stale" state status message from the server.
0
Answers
-
One way would be to configure monitoring system to capture SALTIM & TRDPRC_1 fields and if no updates after a configurable interval, it probably indicates updates are stopped for a particular ric.
That's not how Elektron work.
Elektron send updates only when there is new data. It is possible to not receive any updates all day long for RICs that have no market activity. So, no update doesn't equal to data status down.
If data status down, you should receive a status message from the server.
What made you believe that data update has stopped?
Did you compare it to another source?
If yes, did the application receive any status message?
Have you tried enabling message tracing and see if the application received any status message?
0 -
@Warat, Thanks for the reply. Sorry I was not clear. We could check the most active/liquid RICs of a particular market. Again this may not yield 100% accurate outcome regarding the data status but it does give some indication as to the update status.
We wish to implement such type of monitoring so it would be helpful if you can advise status messages sent by ERT / TREP components which can be captured with the API(e.g. RFA C++).
Thank you.
0 -
Basically, the status consists of Stream State and Data State.
The stream state indicates the state of the stream (e.g., Open, Closed) while the data state indicates the validity of the data (e.g., OK, Suspect).
The status combinations that you would see when updates stopped are either
- Stream: OPEN / Data: SUSPECT or
- Stream: CLOSED / Data: SUSPECT
The first one means data is temporarily unavailable. It can recover itself, which you will then receive a refresh message contain the current data with Stream: Open Data: Ok status.
The second one means Data is not available and is not likely to become available. This usually sent as a result of permission denied or incorrect request rather than data issue, and you should check the accompanying status text for more info.
For RFA C++, you should check out section "7.4.2 Response Status" of DevGuide for more detail.
When you process response message, you should always check for Status Flag and then get the Stream and Data state of the item.
if(respMsg.getHintMask() & RespMsg::RespStatusFlag)
{
const RespStatus& status = respMsg.getRespStatus();
status.getStreamState(); // This return Stream State Enum
status.getDataState(); // This return Data State Enum
status.getStatusText(); // This return string describe the status.
}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 中文论坛