Logging for EMA API

Regarding the logging of the EMA SDK, is there a way to capture the logging and put in our own format. See below from the example showed.

Client notice they can implement the IOmmConsumerErrorClient, this has three methods that you can override OnInvalidHandler, OnOnvalidUsage and OnDisaptch. When Client simulate a network outage locally None of these methods are trigger only the console output. How do Client handle this and capture these events which are outputted to the console (see below for examples)

WARN|: loggerMsg

ClientName: ChannelCallbackClient

Severity: Warning Text: Received ChannelDownReconnecting event on channel Channel_4

Instance Name Consumer_4_1

Channel is null

Error Id SUCCESS

Internal sysError 0

Error Location Reactor.ProcessReactorEventImpl

Error text Reconnection failed: Failed REST request for the service discovery. Text: One or more errors occurred. (No such host is known. (api.refinitiv.com:443)) Client channel has connection attempts left

loggerMsgEnd

WARN|: loggerMsg

ClientName: ChannelCallbackClient

Severity: Warning Text: Received Channel warning event on channel Channel_4

Instance Name Consumer_4_1

Channel is null

Error Id SUCCESS

Internal sysError 0

Error Location ReactorTokenSession.RestErrorCallback

Error text Failed REST request for the service discovery. Text: One or more errors occurred. (No such host is known. (api.refinitiv.com:443))

loggerMsgEnd

WARN|: loggerMsg

ClientName: ChannelCallbackClient

Severity: Warning Text: Received ChannelDownReconnecting event on channel Channel_4

Instance Name Consumer_4_1

Channel is null

Error Id SUCCESS

Internal sysError 0

Error Location Reactor.ProcessReactorEventImpl

loggerMsgEnd

Find more posts tagged with

logging

#technology

Accepted answers

All comments

Jirapongse

@tzewen.ng

Thank you for reaching out to us.

Is this related to EMA C++, EMA Java, or EMA C#?

If it is EMA Java, please refer to this Learn how to direct EMA Java log to Java Logging API article.

wasin.w V3

Hello @tzewen.ng

Beside how to capture the log question, the "Failed REST request for the service discovery. Text: One or more errors occurred. (No such host is known. (api.refinitiv.com:443))" means the API cannot access the RDP Service Discovery endpoint because the machine cannot access api.refinitiv.com:443 domain.

The api.refinitiv.com:443 is the Delivery Platform (RDP) DNS. This is most likely a network issue. Does the client organization has any Firewall, Network Policies, Proxys that block access to api.refinitiv.com DNS.

The client can find the api.refinitiv.com static IP address if they need here RDP API Gateway Public URLs.

tzewen.ng

Hi Jirapongse,

Thanks for your reply. The client is using EMA C#.

Jirapongse

@tzewen.ng

I’m unable to find a way to do this in EMA C#.

Please contact the API support team directly via Contact Premium Support to confirm.

Otherwise, the client can raise this question on GitHub.

wasin.w V3

Hello @tzewen.ng

There is the RestEnableLog and RestLogFileName configurations for logging the HTTP REST connection process in the EmaConfig.xml file. This might help the client to capture the API REST process logging.

<Consumer>

	<Name value="Consumer_4"/>


	<!-- ChannelSet specifies an ordered list of Channels to which OmmConsumer will attempt to	-->

	<!-- connect, one at a time, if the previous one fails to connect							-->

	<ChannelSet value="Channel_4"/>

	<Logger value="Logger_1"/>

	<Dictionary value="Dictionary_1"/>

	<XmlTraceToStdout value="0"/>


	<RestEnableLog value="1"/>

	<RestLogFileName value="RestLog.txt"/>

</Consumer>

Example Output:



------ REST REQUEST ------

Time stamp: 2026-01-29 14:28:13.545

Method: POST, RequestUri: 'https://api.refinitiv.com/auth/oauth2/v2/token', Version: 1.1, Content: System.Net.Http.FormUrlEncodedContent, Headers:

{

  Accept: application/json

  Accept-Encoding: gzip

  Accept-Encoding: deflate

  Accept-Encoding: br

  Content-Type: application/x-www-form-urlencoded

  Content-Length: 141

}

Content: 

grant_type=client_credentials&scope=trapi.streaming.pricing.read&client_id=my_client_id&client_secret=***********

------     END      ------



------ REST RESPONSE ------

Time stamp: 2026-01-29 14:28:13.550

StatusCode: 200, ReasonPhrase: 'OK', Version: 1.1, Content: System.Net.Http.HttpConnectionResponseContent, Headers:

{

  Date: Thu, 29 Jan 2026 07:28:13 GMT

  Connection: keep-alive

  X-Amzn-Trace-Id: Root=1-697b0c0d-11e16a975c839ea006986c6c

  X-Served-By: region=ap-southeast-1; cid=930b5d3e621348aaa5cfddf251c5f43a

  X-Tr-Requestid: 2caffca6-bc35-444a-85c0-0bb338702ecc

  Content-Type: application/json

  Content-Length: 90

}

Content: 

{ "expires_in":7199, "token_type":"Bearer", "access_token":"access token"}

------     END      ------



------ REST REQUEST ------

Time stamp: 2026-01-29 14:28:14.121

Method: GET, RequestUri: 'https://api.refinitiv.com/streaming/pricing/v1/?transport=tcp&dataformat=rwf', Version: 1.1, Content: <null>, Headers:

{

  Accept: application/json

  Accept-Encoding: gzip

  Accept-Encoding: deflate

  Accept-Encoding: br

  Authorization: Bearer access token

}

------     END      ------



------ REST RESPONSE ------

Time stamp: 2026-01-29 14:28:14.122

StatusCode: 200, ReasonPhrase: 'OK', Version: 1.1, Content: System.Net.Http.DecompressionHandler+GZipDecompressedContent, Headers:

{

  Date: Thu, 29 Jan 2026 07:28:13 GMT

  Connection: keep-alive

  Access-Control-Allow-Origin: *

  Access-Control-Expose-Headers: content-encoding, content-length, x-tr-requestid, x-tr-correlationid

  X-Amzn-Trace-Id: Root=1-697b0c0d-7c4d0e6d37a993ad0a380251

  X-Served-By: region=ap-southeast-1; cid=13c0700927574419abdaf5032ec8560a

  X-Tr-Requestid: d0f01f5c-f431-44a5-a559-0d0aa6b67975

  Content-Type: application/json; charset=utf-8

}

Content: 

{"services":[{"port":14002,"location":["ap-northeast-1a"],"transport":"tcp","provider":"aws","endpoint":"ap-northeast-1-aws-1-sm.optimized-pricing-api.refinitiv.net","dataFormat":["rwf"]},...]}

------     END      ------

EXPLORE OUR SITES