> For the complete documentation index, see [llms.txt](https://docs.tailer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tailer.ai/data-pipeline-operations/monitoring-and-alerting.md). # Monitoring and Alerting ## ✅ Compatible data operations All data operation runs can be monitoring and send an alert when it failed ## ⚙️ How it works You can enriched the configuration of any data operation with monitoring and alerting information in order to define criteria about the data operation criticality when it failed. Those information also determine if Tailer should send an alert, when to who and with which specific content. ## **📋 How to monitor data operation runs and send an alert** The monitoring and alerting parameters of a data operation are defined inside the data operation configuration, at the root level under the `monitoring {}` json object. that's mean you have to redeploy a data operation configuration to activate monitoring and alerting triggers. You can use specific variables in your alerting messages in order to generate, for instance, an email following your monitoring requirements. But, you can also use the default tailer alerting templates so you don't have to build your own message. To learn about the Monitoring and Alerting parameters, refer to [this page](/data-pipeline-operations/orchestrate-processings-with-workflow/workflow-configuration-file.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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.tailer.ai/data-pipeline-operations/monitoring-and-alerting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.