> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/uof/sdk/features/logging.md). # Logging The SDK logging component is configured via a configuration file for the selected logging platform. The examples available at 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)](/uof/sdk/languages/java/common-logs-explained.md) #### 2. [Example Logs (.NET)](/uof/sdk/languages/.net/common-logs-explained.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.sportradar.com/uof/sdk/features/logging.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.