---
schema_version: "1"
id: 3b887b733b2031fbe13879ef3242ce4f71641bcb48eeb1e0549fb9ba6475e18c
title: Reviewing Alerts Concepts
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/api-manager/latest/using-api-alerts.md
canonical_url: https://docs.mulesoft.com/api-manager/latest/using-api-alerts
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 0e52f2af9aefb8635c9583542f48c1a4a6225438db46c2603df821e50c0be412
description: MuleSoft Documentation Site
release: 2.x
latest: true
---
---
product: API Manager
version: 2.x
is-latest-version: true
keywords: alerts, instance, api alerts, contracts
---

# Reviewing Alerts Concepts

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Anypoint Platform alerts you about request behavior, performance issues, actions related to client
application contracts, and runtime events.

The platform supports three types of alerts:

- Instance alerts

- Contracts alerts

- Runtime alerts

Instance alerts and contracts alerts are managed by Anypoint API Monitoring. Runtime alerts are
managed by Anypoint Runtime Manager (Runtime Manager). Refer to
[Using Omni Gateway API Alerts](https://docs.mulesoft.com/gateway/latest/use-api-alerts) to learn how to use the new API
Monitoring alerts.

> [!NOTE] Alerts aren’t available on Hyperforce deployments.

## Instance Alerts

Add and configure instance alerts that flag unusual behavior, such as:

- A response time over 60 seconds

- More than 1000 requests in 30 seconds

See [Add Instance Alerts in API Manager (Mule Gateway)](https://docs.mulesoft.com/api-manager/latest/add-api-alert-task).

API Manager enables you to add alerts to different types of instances:

- For **API instances**:

  - **Policy Violation** An infraction of one or more policies governing the API occurs.

  - **Request Count** Users request access to the API more times than allowed in a specified
    interval of time. Specify time interval values from 1 through 999999999. To prevent data bursts,
    intervals are implemented as sliding windows instead of as absolute minute boundaries. See
    [Sliding Windows](https://www.techopedia.com/definition/869/sliding-window).

  - **Response Code** The API returns one of these HTTP codes upon receiving a request: 400, 401,
    403, 404, 408, 500, 502, or 503.

  - **Response Time** The response time of the API exceeds a specified timeout period.

- For **Agent Fabric assets (agents, MCP servers, LLMs)**:

  - Availability or connectivity issues.

  - Broker or agent failure events.

  - Processing delays or exceeded capacity thresholds.

Instance alerts are triggered only when states change, although the first occurrence of a state
change might be undetected due to newly created alerts not having defined states.

When configuring an instance alert, you select Business Group users to receive email notifications
about the alert. Notifications include information about events that trigger alerts as specified by
severity level. Users receive the following:

- One email describes the alert:

  `Your API, CesarDemoAPI - Basic:151 (Environment: "NewOne"), has received greater than 2 requests within 1 consecutive periods of 1 minute.`

- Another email notifies you when the alert is resolved:

  `Your API Version, jsonplaceholderapi - 1.0.development, is no longer in an alert state. The number of policy violations was not greater than 1 in the last 1 consecutive periods of 1 minute.`

After an alert is triggered, API Manager sends the first set of two notification emails and stops
listening for alerts until the next alert period begins. This technique prevents repeated
notification emails.

> [!NOTE] Alerts are sent from `no-reply@mulesoft.com`. This cannot be customized.

The alert email can be sent before the corresponding sliding window has fully closed.  
Although the alert condition is evaluated based on the sliding window, the condition may be met
before all metrics for the window arrive. For example: If the alert condition is set to "error
count > 1 in a 5-minute window" and 10 errors occur within the first minute, the alert email is sent
during that first minute, even though the sliding window continues to accumulate metrics for the
remaining 4 minutes.

## Contracts Alerts

API Manager automatically notifies users when actions related to contracts occur. For instance, when
a client application requests access to an instance, API Manager sends a notification with the
status of the request. Depending on the configuration, status might indicate that the request is
pending manual approval, or it might indicate that the request has been auto-approved.

The following actions trigger contracts alerts:

<table><caption>Table 1. Contracts</caption> <colgroup><col> <col> <col></colgroup><thead><tr><th>Action</th><th>Recipient</th><th>Description</th></tr></thead><tbody><tr><td><p>Contract approved</p></td><td><p>Client application owners</p></td><td><p>User is notified that request access was approved.</p></td></tr><tr><td><p>Contract auto-approved</p></td><td><p>Organization administrators, environment administrators, contracts managers</p></td><td><p>User is notified that request access was auto-approved.</p></td></tr><tr><td><p>Contract pending</p></td><td><p>Organization administrators, environment administrators, contracts managers</p></td><td><p>User is notified that request access is pending.</p></td></tr><tr><td><p>Pending contract rejected</p></td><td><p>Client application owners</p></td><td><p>User is notified that request access was rejected.</p></td></tr><tr><td><p>Revoked contract restored</p></td><td><p>Client application owners</p></td><td><p>User is notified that request access was restored.</p></td></tr><tr><td><p>Approved contract revoked</p></td><td><p>Client application owners</p></td><td><p>User is notified that request access was revoked.</p></td></tr><tr><td><p>Contract tier changed</p></td><td><p>Client application owners</p></td><td><p>User is notified that the contract tier was changed.</p></td></tr><tr><td><p>Requested contract tier change approved</p></td><td><p>Client application owners</p></td><td><p>User is notified that a requested tier change was approved.</p></td></tr><tr><td><p>Requested contract tier change rejected</p></td><td><p>Client application owners</p></td><td><p>User is notified that a requested tier change was rejected.</p></td></tr><tr><td><p>Contract tier change requested</p></td><td><p>Organization administrators, environment administrators, contracts managers</p></td><td><p>User is notified that a contract tier change is pending review.</p></td></tr></tbody></table>

<table><caption>Table 2. Group Contracts</caption> <colgroup><col> <col> <col></colgroup><thead><tr><th>Action</th><th>Recipient</th><th>Description</th></tr></thead><tbody><tr><td><p>Contract approved</p></td><td><p>Client application owners</p></td><td><p>User is notified that request access was approved.</p></td></tr><tr><td><p>Contract auto-approved</p></td><td><p>Group administrators</p></td><td><p>User is notified that request access was auto-approved.</p></td></tr><tr><td><p>Approved contract revoked</p></td><td><p>Client application owners</p></td><td><p>User is notified that request access was revoked.</p></td></tr><tr><td><p>Revoked contract restored</p></td><td><p>Client application owners</p></td><td><p>User is notified that request access was restored.</p></td></tr><tr><td><p>Pending contract rejected</p></td><td><p>Client application owners</p></td><td><p>User is notified that request access was rejected.</p></td></tr><tr><td><p>Contract pending</p></td><td><p>Group administrators</p></td><td><p>User is notified that request access is pending.</p></td></tr><tr><td><p>Contract tier changed</p></td><td><p>Client application owners</p></td><td><p>User is notified that a contract tier change is pending review.</p></td></tr><tr><td><p>Requested contract tier change approved</p></td><td><p>Client application owners</p></td><td><p>User is notified that a requested tier change was approved.</p></td></tr><tr><td><p>Requested contract tier change rejected</p></td><td><p>Client application owners</p></td><td><p>User is notified that a requested tier change was rejected.</p></td></tr><tr><td><p>Contract tier change requested</p></td><td><p>Group administrators</p></td><td><p>User is notified that a contract tier change is pending review.</p></td></tr></tbody></table>

> [!NOTE] Contracts Alerts are sent from `no-reply@mulesoft.com`. This cannot be customized.

## Runtime Alerts

Alerts in Runtime Manager differ from API alerts and contracts alerts. For example, Runtime Manager
flags CPU usage, secure data gateway status, and deployment success or failure. See
[Alerts](https://docs.mulesoft.com/runtime-manager/alerts-on-runtime-manager).

## Omni Gateway Alerts

Alerts for Omni Gateway differ from API alerts and contract alerts. For example, Omni Gateway
includes **Alert Logic** options and the ability to customize the subject and message of **Email
notifications**. See [Using Omni Gateway API Alerts](https://docs.mulesoft.com/gateway/latest/use-api-alerts) for more
information.

## Alert Rate Limits

Anypoint Platform enforces rate limits that determine how often an alert is triggered, and how often
email notifications are sent.

See [Rate Limits on Alerts](https://docs.mulesoft.com/runtime-manager/alerts-on-runtime-manager#rate-limits-on-alerts)
for information on enforced limits.

## See Also

- [Add Instance Alerts in API Manager (Mule Gateway)](https://docs.mulesoft.com/api-manager/latest/add-api-alert-task)

- [Testing an API Alert](https://docs.mulesoft.com/api-manager/latest/test-alert-task)

- [Viewing and Deleting API Alerts](https://docs.mulesoft.com/api-manager/latest/view-delete-alerts-task)

- [Editing, Enabling, or Disabling API Alerts](https://docs.mulesoft.com/api-manager/latest/edit-enable-disable-alerts-task)