> 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.md).

# Monitorización e informes

- [Informes de Alarms](https://help.verkada.com/classic-alarms/es/monitorizacion-e-informes/alarms-reports.md): Los informes te permiten recopilar fácilmente información sobre tu sitio de Alarmas.
- [Números de teléfono de monitorización de Verkada](https://help.verkada.com/classic-alarms/es/monitorizacion-e-informes/verkada-monitoring-phone-numbers-for-classic-alarms.md): Guarda los números de teléfono que el equipo de monitorización de Verkada usará para contactarte
- [Uso de ancho de banda de dispositivos de Alarmas clásicas](https://help.verkada.com/classic-alarms/es/monitorizacion-e-informes/classic-alarms-devices-bandwidth-usage.md): Uso de ancho de banda para dispositivos de Alarmas clásicas
- [Eventos de gran volumen](https://help.verkada.com/classic-alarms/es/monitorizacion-e-informes/high-volume-events.md): Aprende ahora a usar eventos de gran volumen
- [Certificado de monitorización de Alarmas clásicas de Verkada](https://help.verkada.com/classic-alarms/es/monitorizacion-e-informes/verkada-classic-alarms-monitoring-certificate.md): Obtén un certificado que indique que tu sitio de alarma está monitorizado


---

# 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.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.