> For the complete documentation index, see [llms.txt](https://docs.economize.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.economize.cloud/product-features/notifications/alerts.md).

# Alerts

Alerts are triggered when cloud spend exceeds predefined thresholds or when unusual cost patterns are identified. There are two types of alerts available:

1. **Cost Alerts:** Notifies when spending reaches or surpasses set limits. 
2. **Anomaly Alerts:** Detect and report unusual spending patterns or sudden cost spikes, using advanced algorithms.

## Information included

Alerts typically include the following data:

<figure><img src="/files/IYZVAgYaqlvEPMNBhVlJ" alt=""><figcaption><p>Cost alert sent to Slack channel</p></figcaption></figure>

| Data                 | Description                                                 |
| -------------------- | ----------------------------------------------------------- |
| Cost deviation       | Indicates the spike or drop in costs                        |
| Projects or accounts | Specifies the projects or accounts affected                 |
| Resource affected    | Identifies the affected services, labels, or SKUs           |
| Percentage change    | Shows the percentage increase or decrease in costs          |
| Cost difference      | Provides the absolute cost difference                       |
| Time period          | Defines the time period over which the cost change occurred |

## Creating an Alert

Navigate to Notifications from the [Economize console](https://www.economize.cloud/app/login) sidebar, and follow the instructions below:

{% hint style="info" %}
The available fields within the Create alerts modal will dynamically update based on the selected alert type, ensuring only relevant options gets configured.
{% endhint %}

{% stepper %}
{% step %}

### Enter Details

* **Alert name:** Enter a descriptive name for your alert.
* **Alert type:** Select from *Cost Alert* or *Anomaly Alert* as the alert type.
* **For:** Choose what the alert should monitor, i.e., Projects, Services, Labels, or SKUs.
* **Filter:** Define the specific resources within the selected criteria of *the "For"* field above.
* **Time Range:** Select how often you want to receive alerts, i.e., daily, weekly, or monthly.

<figure><img src="/files/bOIW61FYGPkDcUJgR1Nr" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Define Scope

* **Threshold:** Set a threshold amount that will trigger the alert.
* **Ignore spend below (optional):** Set a minimum amount to avoid triggering alerts for insignificant or small costs.
* **Include Credits:** Determines whether any applied credits should be factored into cost calculations for alerts.
* **Include Cost DropS:** Choose if you want to be notified of cost decreases as well.
* **Amortization:** Distributes costs evenly across time, rather than recording them only when expenses occur.

{% hint style="warning" %}
Amortization support is available exclusively for **AWS** alerts alone right now.
{% endhint %}

<figure><img src="/files/Td5NtPJTdmls6HThjhP2" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Specify Destination

{% hint style="info" %}
Alerts can be routed to multiple channels or destinations across any [supported integration](/integrations/overview.md). This makes it easy to deliver them to different teams, projects, or groups, depending on your organizational needs. Simply select the desired destinations and channels from the dropdown menu during configuration.&#x20;

![](/files/Yn61PcKLEpzbRdOT4JS5)
{% endhint %}

* **Destination:** Select the workspace tools where you want to receive the budget from the available [integrations](/integrations/overview.md).
* **Channel:** Select the specific channels within the chosen destinations.
  {% endstep %}
  {% endstepper %}


---

# 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.economize.cloud/product-features/notifications/alerts.md?ask=<question>&goal=<endgoal>
```

`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.