How can I capture the error message?

When doing a get_timeseries request, there are times that the RICs list I submitted included some non-valid RICs for one reason or another. Usually do to corporate actions. Some of the sample error message are as follows:
Error with OMAM.N: No data available for the requested date range or Error with LNCE.OQ: Invalid RIC
This error prints out in the ipython console, but I would like to be able to capture these errors so I can create of list of the RIC's that are causing the errors. How would I do this?
I looked at the Eikon Python API reference guide but I cannot figure out how to use the EikonError class to get the information I am after.
Thanks for your help.
Richard
Best Answer
-
get_timeseries method only raises an exception when it cannot retrieve timeseries for all instruments in the list. If get_timeseries succeeds in retrieving timeseries for at least one instrument, then for those instruments where retrieval fails get_timeseries method merely logs a warning.
The only way I know to capture messages created by a Python logger is by adding a handler to the logger. Here's an example you can easily adapt for your purpose:
http://alanwsmith.com/capturing-python-log-output-in-a-variable
The name of the logger that eikon package utilizes is 'pyeikon'. You can get it by calling logging.getLogger('pyeikon')0
Answers
-
Hi @richard.jones2,
The get_timerseries() call does document it will throw an exception upon an error. So when I tried this, I do see the exception being thrown when I define an invalid symbol:
However, when I include a valid symbol within my list, as you did, an exception is not thrown.
In both cases, we can see the error message within the console - as you observed. Let me reach out to the product team to determine what is expected and how an application is expected to trap this issue.
0 -
thanks Alex
0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 683 Datastream
- 1.4K DSS
- 613 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 248 ETA
- 552 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 626 Refinitiv Data Platform Libraries
- 5 LSEG Due Diligence
- 1 LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 84 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛