> For the complete documentation index, see [llms.txt](https://docs.skyone.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skyone.cloud/espanol/skyone-studio/vision-general/organizaciones/monitoreo-de-la-organizacion.md).
# Monitoreo de la Organización
El área de Monitoreo permite visualizar las ejecuciones y el consumo de GIGS, tanto a nivel de Organización como por espacio, facilitando la administración de recursos
### Panel de resumen
Muestra un resumen con los principales datos del espacio de trabajo, incluyendo:
* **Consumo:** total de GIGS (datos) consumidos en el período seleccionado
* **Integraciones activas**: total de integraciones que están activas.
* **Ejecuciones totales**: total de ejecuciones en el período seleccionado.
* **Integraciones con fallas:** cantidad total de fallas en el período seleccionado.
* **Datos transferidos**: tráfico total de datos en el período seleccionado.
### Visión general
En esta área es posible seguir los siguientes gráficos:
* **Ejecuciones y fallas**
* **GIGS**
* **Ejecuciones**
* **Tráfico**
* **Flujos**
Lee más en el artículo "[Monitoreo](/espanol/skyone-studio/monitoreo.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.skyone.cloud/espanol/skyone-studio/vision-general/organizaciones/monitoreo-de-la-organizacion.md?ask=&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.