> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/docs/fr/votre-espace-de-travail/monitoring.md).

# Surveillance

Surveillez les analytics des workflows, les alertes et l'historique des exécutions dans tout votre espace de travail.

La surveillance vous aide à examiner les performances des workflows, à réagir aux échecs et à consulter l’historique des exécutions dans l’ensemble de votre espace de travail.

## Performance

Utiliser [Analytique](/docs/fr/votre-espace-de-travail/monitoring/analytics.md) pour comprendre le volume d’exécution des workflows, la latence et les tendances des tâches. Pour la consommation des tâches Workflow, Playbook, Answer et de test à l’échelle de l’espace de travail, voir [Utilisation](/docs/fr/votre-espace-de-travail/settings/usage.md).

## Alertes et historique des exécutions

Utiliser [Alertes](/docs/fr/votre-espace-de-travail/monitoring/alerts.md) pour recevoir des notifications lorsqu’un workflow échoue. Utilisez [Historique des exécutions](/docs/fr/votre-espace-de-travail/monitoring/run-history.md) pour consulter les exécutions passées des workflows et réessayer les exécutions en erreur.


---

# 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.airops.com/docs/fr/votre-espace-de-travail/monitoring.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.