> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/classic-alarms/es/monitorizacion-e-informes/alarms-reports.md).

# Informes de Alarms

Los informes te permiten recopilar fácilmente información sobre tu sitio de Alarmas.

{% hint style="success" %}
Verkada anunció el fin global de la venta (1 de agosto de 2026) y el fin de vida (1 de agosto de 2027) de Classic Alarms. Los clientes elegibles pueden actualizarse a New Alarms sin costo hasta el 31 de enero de 2027. Visite [Verkada.com/alarms/upgrade](https://www.verkada.com/alarms/upgrade) para comenzar.
{% endhint %}

El **Informes** La página en Verkada Command te permite:

* Obtén una vista rápida de todos los eventos de alarma en tu organización.
* Personaliza el informe para filtrar eventos específicos.
* Exporta el informe como un archivo de valores separados por comas (CSV) para un análisis adicional o para grabar registros.

***

## **Crear informes de Alarmas**

{% stepper %}
{% step %}
**En Verkada Command, ve a Todos los productos > Alarmas.**
{% endstep %}

{% step %}
**En la navegación de la izquierda, selecciona Informes.**
{% endstep %}

{% step %}
**En la parte superior, selecciona una de las opciones de informe de Alarmas.**
{% endstep %}

{% step %}
**(Opcional) haz clic en Filtro para agregar o quitar campos.**
{% endstep %}

{% step %}
**En la parte superior derecha, haz clic en Exportar.**
{% endstep %}
{% endstepper %}

***

## Exportar informes

Para exportar un archivo CSV del informe que generaste, en la parte superior derecha, haz clic en **Exportar** ![](https://2810967188-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9tIFgMOGbY4p9wWaKQhl%2Fuploads%2Fgit-blob-e3d3abfd7841ea51a6f0350a4d4ddc89912bbfcc%2F0fc471f10b17823b3076f1f060c56c0d531acabf.png?alt=media).


---

# 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://help.verkada.com/classic-alarms/es/monitorizacion-e-informes/alarms-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.