> 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/concepts/intermediate-concepts/reports.md).

# Informes

Los informes de Devolutions Server resumen datos de actividad como inicios de sesión fallidos, uso de contraseñas y consumo de licencias para revisiones de cumplimiento normativo.

Los informes de Devolutions Server ofrecen vistas resumidas de la actividad y la configuración para que pueda responder rápidamente a preguntas operativas y de cumplimiento normativo. Se generan a partir de datos de registro y de auditoría y pueden destacar elementos como inicios de sesión fallidos, uso de contraseñas, consumo de licencias o actividad específica de un módulo.

Los administradores y los auditores pueden ejecutar informes a demanda o programarlos, exportando los resultados cuando sea necesario para una revisión externa. Por ejemplo, un equipo de seguridad podría generar un informe mensual de las extracciones de cuentas privilegiadas y las sesiones remotas asociadas para satisfacer los requisitos de auditoría.

#### Temas relacionados

* [Informes](/server/es/web-interface/utilities/reports.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.devolutions.net/server/es/concepts/intermediate-concepts/reports.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.