Logging

The SDK logging component is configured via a configuration file for the selected logging platform. The examples available at http://sdk.sportradar.com use logback (Java) and log4net ( .NET) and can serve as a reference for configuring those two logging platforms.

The actual logging platform must be provided by the user via a dependency management system. Since the investigation of possible SDK issues relies on the logs generated by the SDK, the users are encouraged to keep the logs for longer periods and have them configured to log as much information as possible (especially during the integration)

SDK logs data to multiple files, and different levels can be assigned to different loggers.

• Execution log: contains log entries providing information on the SDK flow for a given moment

• Interaction log: logs the user interaction with the SDK. This includes when a key method on an SDK's public interface is invoked or when a message is dispatched to the user.

• Rest traffic: logs all requests to the Sports API and the associated responses. This can produce a lot of log entries, so the users are encouraged to decrease the level once in production

• Feed traffic: logs all messages received from the AMQP broker. This can produce a lot of log entries so the users are encouraged to decrease the level once in production

• Traffic failure: Logs the messages that could not be dispatched to the user.

Below are sample logs demonstrating how the SDK records activities across its various log files, with examples provided for both Java and .NET implementations:

1. Example Logs (Java)

2. Example Logs (.NET)