> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/products/edgesight/alerts.md).
# Alerts
Learn about Edgesight Alerts and how it detects CDN traffic anomalies and delivers real-time notifications.
Edgesight Alerts is a proactive monitoring solution that detects anomalies in CDN traffic in real time. When an issue occurs in the traffic , a sudden spike in errors, an unexpected drop in cache efficiency, or a slowdown in origin server response times , the anomaly is automatically detected, and a notification is delivered through the configured channels (Slack, email, or webhook).
{% hint style="success" %}
Rather than continuously monitoring dashboards, notifications are received only when attention is required.
{% endhint %}
Edgesight Alerts allows you to define customized and intelligent alarm rules based on the behavioral patterns of CDN traffic.
{% hint style="success" %}
Edgesight Alerts integrates with [Edgesight Analytics](/products/edgesight/analytics.md) to deliver richer alerting capabilities.
{% endhint %}
Edgesight Alerts revolves around three core processes: **alert creation**, **alert editing**, and **alert management**. The details of each process are covered in separate documents:
* [**Alert Management**](/products/edgesight/alerts/alert-management.md) — Overview Dashboard, alert list, enabling/disabling, editing, testing, and deleting alerts
* [**Create Alert**](/products/edgesight/alerts/create-alert.md) — Defining a new alert through the 4-step wizard
---
# 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://clients.medianova.com/products/edgesight/alerts.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.
