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

# Habilitar los registros HTTP de Devolutions Server

Habilite el registro de solicitudes y respuestas HTTP en Devolutions Server editando appsettings.json para hacer un seguimiento de la actividad en el fichero de registro DPS\_Main.

Los registros HTTP de Devolutions Server ayudan a hacer un seguimiento de las solicitudes y respuestas HTTP, así como de otras propiedades comunes.

Para habilitar los registros HTTP, primero [deben habilitarse los ficheros de registro de Devolutions Server en la Devolutions Server Console](/server/es/knowledge-base/how-to-articles/enable-the-devolutions-server-log-files.md). Una vez hecho esto, vaya a **C:\inetpub\wwwroot\dvls**, abra **appsettings.json** y cambie la línea ***"Devolutions": "Information"*** por ***"Devolutions": "Debug"***.

Las solicitudes HTTP deberían registrarse entonces en el fichero **DPS\_Main.log** ubicado en **C:\inetpub\wwwroot\dvls\App\_Data**.

{% hint style="warning" %}
Tenga en cuenta que habilitar el registro HTTP puede reducir el rendimiento. Úselo con precaución.
{% 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/es/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.