> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-admin-guide/parallels-ras-21-administrators-guide/virtual-desktop-infrastructure-vdi/configure-logging.md).

# Configure logging

To configure logging and retrieve or clear existing log files, right-click a Provider, choose **Troubleshooting** > **Logging** in the context menu, and then click one of the following, depending on what you would like to do: **Configure**, **Retrieve**, or **Clear**. For the information on how to perform these tasks, see the [**Logging**](/landing/ras-admin-guide/parallels-ras-21-administrators-guide/common-management-tasks/logging.md) section. Please also read the important information below.

Note that logging of Provider operations is performed on the RAS Provider Agent level. When you configure logging for a Provider, you are essentially configuring it for the RAS Provider Agent that services this Provider. This means that if you are using the built-in RAS Provider Agent, its logging configuration applies to all Providers that it services. Consider the following scenarios:

* When you retrieve log files for a specific Provider serviced by the built-in Provider Agent, the files will contain logs for all Providers serviced by the same agent.
* If you clear log files for a particular Provider, you should be careful because the logs will be cleared for all Providers if they are serviced by the same built-in Provider Agent. The RAS Console will prompt you if you try to delete such a shared log.

If a Provider has a dedicated Provider Agent, which services this host only, none of the above applies.


---

# 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.parallels.com/landing/ras-admin-guide/parallels-ras-21-administrators-guide/virtual-desktop-infrastructure-vdi/configure-logging.md?ask=<question>&goal=<user_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.