> For the complete documentation index, see [llms.txt](https://docs.itconductor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itconductor.com/overview/monitoring-concepts/application-performance-management/alerts-management.md).
# Alerts Management
Most monitoring solutions treat alerts as raw events without much context or relationship.
Figure 1: Root Cause Analysis
IT-Conductor manages alerts more effectively by using policy-based exceptions where alerts can be filtered, time-synchronized, and automatically recovered, including targeted notification to the right analyst reducing mean time to repair (MTTR).
Alerts are configured in IT-Conductor using the concept of [thresholds and overrides](/overview/monitoring-concepts.md).
See [Creating Threshold Overrides](/user-guide/notifications/threshold-overrides.md) for more information.
After setting up the IT-Conductor Gateway and configuring the required parameters for the monitored systems, the platform will start receiving different metrics. Using thresholds and overrides, IT-Conductor can send out alert notifications via e-mail, provided that the user has subscribed to receive notifications for that specific service.
---
# 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.itconductor.com/overview/monitoring-concepts/application-performance-management/alerts-management.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.
