> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/it/knowledge-base/how-to-articles/enable-devolutions-server-http-logs.md).

# Abilitare i log HTTP di Devolutions Server

Abiliti la registrazione delle richieste e delle risposte HTTP in Devolutions Server modificando appsettings.json per tracciare l'attività nel file di log DPS\_Main.

I log HTTP in Devolutions Server aiutano a tenere traccia delle richieste e delle risposte HTTP, nonché di altre proprietà comuni.

Per abilitare i log HTTP, è necessario prima [abilitare i file di log di Devolutions Server nella Devolutions Server Console](/server/it/knowledge-base/how-to-articles/enable-the-devolutions-server-log-files.md). Una volta fatto questo, vada in **C:\inetpub\wwwroot\dvls**, apra **appsettings.json** e modifichi la riga ***"Devolutions": "Information"*** in ***"Devolutions": "Debug"***.

Le richieste HTTP dovrebbero quindi essere registrate nel file **DPS\_Main.log** situato in **C:\inetpub\wwwroot\dvls\App\_Data**.

{% hint style="warning" %}
Tenga presente che l'abilitazione della registrazione HTTP può ridurre le prestazioni. Utilizzi con cautela.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/server/it/knowledge-base/how-to-articles/enable-devolutions-server-http-logs.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 `build a script that syncs our docs to a CMS` 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.