EMA programmatic configuration

Map config, map;
ElementList elements;
elements.addAscii ("DefaultConsumer", "Consumer_1");
map.addKeyAscii ("Consumer_1", MapEntry::AddEnum,
ElementList ().addAscii ("Logger", "Logger_1")
.complete ()).complete();
elements.addMap ("ConsumerList", map).complete ();
map.clear ();
config.addKeyAscii ("ConsumerGroup", MapEntry::AddEnum, elements);
elements.clear ();
map.addKeyAscii ("Logger_1", MapEntry::AddEnum,
ElementList ().addEnum ("LoggerType", 1) // stdout
.addEnum ("LoggerSeverity", 3) // errors
.complete ())
.complete ();
elements.addMap ("LoggerList", map).complete ();
map.clear ();
config.addKeyAscii ("LoggerGroup", MapEntry::AddEnum, elements).complete ();
OmmConsumer consumer (OmmConsumerConfig ().username (user.c_str ())
.host (source.c_str ())
.config (config));
I would like to configure the EMA logger to output errors only and to stdout. However the code above causes the logger to output (to stdout) that it there is no logger configuration and defaults will be used - error see below.
Modifying the config to output to file, correctly outputs to file but error persists, albeit in the output file.
Can anyone say why the error below is logged?
The code above is a modified version of the EMA sample 421_MarketPrice_ProgrammaticConfig.
loggerMsg
TimeStamp: ...
ClientName: EmaConfig
Severity: Error
Text: no configuration exists for consumer logger [LoggerGroup|LoggerList|Logger.Logger_1|]; will use logger defaults
loggerMsgEnd
Best Answer
-
EMA prints this log message because it could not find Logger_1 from the EmaConfig.xml file. This is the current behavior that EMA prints out log message when EMA could not find parameters from EMAConfig.xml
The programmatic configuration should still work correctly, even though this error is generated. You can refer to this question.
0
Answers
-
Thanks for your answer.
Given my application works fine without a config file and only outputs an complains about the missing config file when the logger configuration is programmatically modified, I think this behaviour should be marked as a bug to be fixed.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 684 Datastream
- 1.4K DSS
- 615 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
- 249 ETA
- 554 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
- 643 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- 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
- 192 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛