> 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/fr/knowledge-base/how-to-articles/enable-devolutions-server-http-logs.md).

# Activer les journaux HTTP de Devolutions Server

Activez la journalisation des requêtes et des réponses HTTP dans Devolutions Server en modifiant appsettings.json pour suivre l'activité dans le fichier journal DPS\_Main.

Les journaux HTTP dans Devolutions Server aident à suivre les requêtes et les réponses HTTP, ainsi que d'autres propriétés communes.

Pour activer les journaux HTTP, [les fichiers journaux de Devolutions Server doivent d'abord être activés dans la Devolutions Server Console](/server/fr/knowledge-base/how-to-articles/enable-the-devolutions-server-log-files.md). Une fois cela fait, allez à **C:\inetpub\wwwroot\dvls**, ouvrez **appsettings.json**, et changez la ligne ***"Devolutions": "Information"*** pour ***"Devolutions": "Debug"***.

Les requêtes HTTP devraient ensuite être journalisées dans le fichier **DPS\_Main.log** situé dans **C:\inetpub\wwwroot\dvls\App\_Data**.

{% hint style="warning" %}
Notez que l'activation de la journalisation HTTP peut réduire la performance. À utiliser avec précaution.
{% 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 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/fr/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 `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.