*This page
applies to **Apigee** and **Apigee hybrid**.*


*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*
![](https://fonts.gstatic.com/s/i/googlematerialicons/help/v13/gm_grey-24dp/1x/gm_help_gm_grey_24dp.png)

When operations anomalies detects an anomaly, it displays the event in the
[operations anomalies dashboard](https://docs.cloud.google.com/apigee/docs/api-platform/analytics/investigate-anomalies.md.txt). However, it doesn't automatically raise an alert for the anomaly.

If you want to be notified about operations anomalies, you can create an anomaly alert
and notification.

When creating anomaly alerts, you don't need to define the exact conditions
for each anomaly yourself. Operations anomalies determines the right anomaly conditions using
statistical methods, and updates them based on recent traffic data.

## Before you begin

To use anomaly alerts, first make sure your project and your user account meet the requirements in
[Prerequisites for using operations anomalies](https://docs.cloud.google.com/apigee/docs/api-platform/analytics/operations-anomalies-overview.md.txt#prerequisites-for-using-operations-anomalies).

### Create anomaly alerts

In the Google Cloud console, go to the **Monitoring \> Alerting \> Policies** page.

[Go to Policy Configuration Mode](https://console.cloud.google.com/monitoring/alerting/policies/create)

See the [Alerting overview](https://cloud.google.com/monitoring/alerts) instructions for using Alerting policy dashboard.

For Apigee operations anomalies alerting:

- Select **Apigee anomaly event count** as the metric.
- In the **Configure alert trigger** window, set the **Threshold** to **0.5**. (Any number between 0 and 1 will work for the threshold.) With this value, a single anomaly exceeds the threshold and triggers the alert.