---
schema_version: "1"
id: ce4ef14951d5799743c3a96b2aa92d99ce2ffa0be5f077bd847f18f505c50781
title: Creating Alerts for Servers, Server Groups, and Clusters
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/hybrid-standalone/creating-alerts-hybrid.md
canonical_url: https://docs.mulesoft.com/hybrid-standalone/creating-alerts-hybrid
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 9f0a22f87ef532a387d0a53b7ace3e6216d8cf0d77d2633e383975fb8201e133
description: MuleSoft Documentation Site
latest: true
---
---
product: Hybrid Standalone Runtimes
---

# Creating Alerts for Servers, Server Groups, and Clusters

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

Configure proactive monitoring alerts for your hybrid standalone infrastructure to ensure optimal
performance, detect issues early, and maintain system reliability across your distributed Mule
runtime environment.

## Overview

Runtime Manager alerts for hybrid standalone servers are event alerts, such as server connected,
disconnected, or deleted.

On US Cloud and EU Cloud, Runtime Manager also provides metric threshold alerts for CPU, memory,
load average, and thread count. Alerts based on metrics on Canada Cloud, Japan Cloud, India Cloud,
and Australia Cloud come from Anypoint Monitoring, not from Runtime Manager. See
[Getting Alerts](https://docs.mulesoft.com/monitoring/alerts-hf) in Anypoint Monitoring.

> [!NOTE] On Canada Cloud, Japan Cloud, India Cloud, and Australia Cloud, Runtime Manager monitoring
> for hybrid standalone deployments isn’t available. Runtime Manager alerts on those control planes
> are limited to event alerts.
>
> For metric-based alerts, such as CPU usage, memory usage, and resource utilization, use Anypoint
> Monitoring. Basic and advanced Anypoint Monitoring alerts vary by control plane. See
> [Features Supported on Hyperforce](https://docs.mulesoft.com/hyperforce/#features-supported-on-hyperforce).
>
> Runtime Manager retains 30 days of alert history for audit and analysis.
>
> Alerts retrigger when conditions continuously exceed specified thresholds, ensuring persistent
> notification of ongoing issues.

## Rate Limits on Alerts

Anypoint Platform enforces rate limits that determine how often an alert is triggered and prevent
excessive emails from being sent. At present, there is no defined limit to the number of Runtime
Manager alerts.

## Create an Alert

Configure alerts to monitor your servers, server groups, and clusters with customizable thresholds
and notification settings.

1.  In Runtime Manager, click **Alerts**.

    - If no alerts exist, you see the initial setup page:

      ![Alerts page with no alerts set up](/mulesoft/current/en-us/hybrid-standalone/_images/alerts-no-alerts.png)

      Figure 1. The arrow shows the **Create your first alert** option.

    - For existing alert configurations, use the add button:

      ![Alerts page with blue plus (+) icon](/mulesoft/current/en-us/hybrid-standalone/_images/alerts-create-additional-alert.png)

      Figure 2. The arrow shows the blue plus (**+**) icon on the **Alerts** page.

2.  Click the blue plus (**+**) icon to create a new alert.

    ![Create an Alert page](/mulesoft/current/en-us/hybrid-standalone/_images/alerts-create-alert.png)

3.  Complete the required fields:

    - **Name**

      Unique and meaningful name for the alert

      The **Name** is limited to 256 characters.

    - **Severity level**

      Severity of the alert: **Critical**, **Warning**, or **Info**

    - **Source**

      The source of the alert: servers

      This field appears only if your Anypoint Platform account supports local servers.

    - **Server type**

      When the source is **Servers**, the type of server: single server, server group, or cluster.

      If your servers aren’t available on your menu, see
      [Servers, Server Groups, and Clusters](https://docs.mulesoft.com/hybrid-standalone/managing-servers).

    - **Servers**

      The server to apply the alert to

    - **Condition**

      The condition that triggers the alert

      The available options depend on whether your alert is linked to a server. Some conditions
      require additional data. See [Alert Conditions](#alert-conditions).

    - **Subject**

      The subject of the alert email to send when the alert is triggered

      The subject can include variables. See [Alert Variables](#alert-variables).

    - **Message**

      The body text for the email to send when the alert is triggered. The message body can include
      variables. See [Alert Variables](#alert-variables).

    - **Recipients**

      The recipients of the alert email

      You can select up to 20 platform user IDs and enter up to 20 email addresses.

4.  Click **Create Alert**.

When an alert condition is triggered, Runtime Manager sends email notifications similar to this:

![Anypoint Platform Alert Notification email](/mulesoft/current/en-us/hybrid-standalone/_images/alerts-alert-email.png)

## Alert Conditions

Configure specific conditions that trigger notifications based on your infrastructure monitoring
requirements. Alert conditions range from simple status notifications to complex performance
threshold monitoring.

### Performance and Resource Monitoring

These metric threshold alerts apply to all infrastructure types (servers, server groups, and
clusters) on US Cloud and EU Cloud. They aren’t available as Runtime Manager alerts on Canada Cloud,
Japan Cloud, India Cloud, and Australia Cloud. Use
[Anypoint Monitoring alerts](https://docs.mulesoft.com/monitoring/alerts-hf) for metric-based monitoring on those control
planes.

These performance alerts apply to all infrastructure types (servers, server groups, and clusters):

Server CPU Usage

Monitor CPU utilization across your infrastructure. Triggers when CPU usage exceeds the specified
percentage for the configured duration.

![Server CPU usage alert condition](/mulesoft/current/en-us/hybrid-standalone/_images/alerts-conditions-servers-cpu.png)

**Configuration:** Set the CPU percentage threshold and monitoring duration.

Server Load Average

Monitor system processing load. Triggers when the average processing load exceeds the specified
threshold for the configured duration.

![Server load average alert condition](/mulesoft/current/en-us/hybrid-standalone/_images/alerts-conditions-servers-load-avg.png)

**Configuration:** Set the load average threshold and monitoring duration.

> [!NOTE] This metric isn’t available on Windows environments.

Server Memory Usage

Track memory consumption across your infrastructure. Triggers when memory usage (in MB) exceeds the
specified threshold for the configured duration.

![Server memory usage alert condition](/mulesoft/current/en-us/hybrid-standalone/_images/alerts-conditions-servers-memory.png)

**Configuration:** Set the memory usage threshold (MB) and monitoring duration.

Server Thread Count

Monitor JVM thread utilization. Triggers when the thread count exceeds the specified level for the
configured duration.

![Server thread count alert condition](/mulesoft/current/en-us/hybrid-standalone/_images/alerts-conditions-servers-thread-count.png)

**Configuration:** Set the thread count threshold and monitoring duration.

These event alerts vary according to the target type (server, server groups, or clusters) and
require no additional parameters. They are available on all control planes that support hybrid
standalone:

Servers

- **Agent version changed**

- **Runtime version changed**

- **Server connected**

- **Server deleted**

- **Server disconnected**

Server Groups

- **Server Group connected**

- **Server Group deleted**

- **Server Group disconnected**

- **Server Group’s node connected**

- **Server Group’s node disconnected**

- **Server added to Server Group**

- **Server removed from Server Group**

Clusters

- **Cluster connected**

- **Cluster deleted**

- **Cluster disconnected**

- **Cluster presents visibility issues**

- **Cluster’s node connected**

- **Cluster’s node disconnected**

- **Server added to Cluster**

- **Server removed from Cluster**

## Alert Variables

Customize alert email subjects and messages using dynamic variables that provide contextual
information about triggered events.

> [!NOTE] You can’t use the character combination `$&` in variable expressions.

<table><caption>Table 1. Variables for Alerts</caption> <colgroup><col> <col> <col></colgroup><thead><tr><th>Alert Category</th><th>Alert Type</th><th>Available Variables</th></tr></thead><tbody><tr><td colspan="2"><div><div><p>All Alerts</p></div></div></td><td><div><div><p><code>${resource}</code> <code>${severity}</code> <code>${state}</code></p></div></div></td></tr><tr><td rowspan="7"><div><div><p>Server Alerts</p></div></div></td><td><div><div><p>All Server Alerts</p></div></div></td><td><div><div><p><code>${name}</code></p></div></div></td></tr><tr><td><div><div><p><strong>Agent version changed</strong></p></div></div></td><td rowspan="2"><div><div><p><code>${oldVersion}</code> <code>${newVersion}</code></p></div></div></td></tr><tr><td><div><div><p><strong>Runtime version changed</strong></p></div></div></td></tr><tr><td><div><div><p><strong>Server CPU usage</strong></p></div></div></td><td rowspan="4"><div><div><p><code>${currentValue}</code> <code>${comparison}</code> <code>${threshold}</code> <code>${location}</code></p></div></div></td></tr><tr><td><div><div><p><strong>Server Load average</strong></p></div></div></td></tr><tr><td><div><div><p><strong>Server Memory average</strong></p></div></div></td></tr><tr><td><div><div><p><strong>Server Thread count</strong></p></div></div></td></tr><tr><td rowspan="9"><div><div><p>Server Group Alerts</p></div></div></td><td><div><div><p>All Server Group Alerts</p></div></div></td><td><div><div><p><code>${name}</code></p></div></div></td></tr><tr><td><div><div><p><strong>Server Group’s node CPU usage</strong></p></div></div></td><td rowspan="4"><div><div><p><code>${memberName}</code> <code>${groupName}</code> <code>${currentValue}</code> <code>${comparison}</code> <code>${threshold}</code> <code>${location}</code> <code>${parentResource}</code> <code>${parentLocation}</code></p></div></div></td></tr><tr><td><div><div><p><strong>Server Group’s node Load average</strong></p></div></div></td></tr><tr><td><div><div><p><strong>Server Group’s node Memory usage</strong></p></div></div></td></tr><tr><td><div><div><p><strong>Server Group’s node Thread count</strong></p></div></div></td></tr><tr><td><div><div><p><strong>Server Group’s node connected</strong></p></div></div></td><td rowspan="4"><div><div><p><code>${memberName}</code> <code>${groupName}</code></p></div></div></td></tr><tr><td><div><div><p><strong>Server Group’s node disconnected</strong></p></div></div></td></tr><tr><td><div><div><p><strong>Server added to Server Group</strong></p></div></div></td></tr><tr><td><div><div><p><strong>Server removed from Server Group</strong></p></div></div></td></tr><tr><td rowspan="9"><div><div><p>Cluster Alerts</p></div></div></td><td><div><div><p>All Cluster Alerts</p></div></div></td><td><div><div><p><code>${name}</code></p></div></div></td></tr><tr><td><div><div><p><strong>Cluster’s node CPU usage</strong></p></div></div></td><td rowspan="4"><div><div><p><code>${memberName}</code> <code>${clusterName}</code> <code>${currentValue}</code> <code>${comparison}</code> <code>${threshold}</code> <code>${location}</code> <code>${parentResource}</code> <code>${parentLocation}</code></p></div></div></td></tr><tr><td><div><div><p><strong>Cluster’s node Load average</strong></p></div></div></td></tr><tr><td><div><div><p><strong>Cluster’s node Memory usage</strong></p></div></div></td></tr><tr><td><div><div><p><strong>Cluster’s node Thread count</strong></p></div></div></td></tr><tr><td><div><div><p><strong>Cluster’s node disconnected</strong></p></div></div></td><td><div><div><p><code>${resource}</code> <code>${memberName}</code> <code>${clusterName}</code></p></div></div></td></tr><tr><td><div><div><p><strong>Cluster’s node connected</strong></p></div></div></td><td rowspan="3"><div><div><p><code>${memberName}</code> <code>${clusterName}</code></p></div></div></td></tr><tr><td><div><div><p><strong>Server added to Cluster</strong></p></div></div></td></tr><tr><td><div><div><p><strong>Server removed from Cluster</strong></p></div></div></td></tr></tbody></table>

<table id="var-defs"><caption>Table 2. Variable Definitions</caption> <colgroup><col> <col></colgroup><thead><tr><th>Variable</th><th>Definition</th></tr></thead><tbody><tr><td><p><code>${clusterName}</code></p></td><td><p>Name of the cluster</p></td></tr><tr><td><p><code>${currentValue}</code></p></td><td><p>Current value of metric that triggers the alert</p></td></tr><tr><td><p><code>${comparison}</code></p></td><td><p>Above or Below</p></td></tr><tr><td><p><code>${groupName}</code></p></td><td><p>Name of the server group</p></td></tr><tr><td><p><code>${location}</code></p></td><td><p>Where to find more information about the alert</p></td></tr><tr><td><p><code>${memberName}</code></p></td><td><p>Name of the node in a server group or cluster</p></td></tr><tr><td><p><code>${name}</code></p></td><td><p>Name of the target (server, server group, or cluster) that triggers the alert</p></td></tr><tr><td><p><code>${newVersion}</code></p></td><td><p>New version number for the agent or runtime</p></td></tr><tr><td><p><code>${oldVersion}</code></p></td><td><p>Previous version number for the agent or runtime</p></td></tr><tr><td><p><code>${parentLocation}</code></p></td><td><p>Where to find more information about the alert on the node’s parent cluster</p></td></tr><tr><td><p><code>${parentResource}</code></p></td><td><p>Name of the resource, such as server or app, on the node’s parent cluster that triggers the alert</p></td></tr><tr><td><p><code>${resource}</code></p></td><td><p>Name of the infrastructure resource that triggers the alert</p></td></tr><tr><td><p><code>${severity}</code></p></td><td><p>Severity of the alert</p></td></tr><tr><td><p><code>${state}</code></p></td><td><p>State of the resource that triggers the alert, such as Running or Disconnected</p></td></tr><tr><td><p><code>${threshold}</code></p></td><td><p>Count over the period of time that triggers the alert</p></td></tr></tbody></table>

## Access and View Alerts

Runtime Manager provides multiple ways to access and monitor your infrastructure alert
configurations and history.

### Global Alert Management

Access all infrastructure alerts from the main alerts dashboard:

1.  Click **Alerts** in the Runtime Manager navigation pane:

    ![Alerts menu](/mulesoft/current/en-us/hybrid-standalone/_images/alerts-view-all-alerts-tab.png)

    Figure 3. The arrow shows the **Alerts** menu.

From the alerts dashboard, you can:

- Create new infrastructure alerts

- Search alerts by name or configuration

- Filter alerts by source, condition, severity, or status

- Modify alert configurations by clicking alert names

- View alert status, settings, and trigger history in the details pane:

  ![Alert history in the details pane](/mulesoft/current/en-us/hybrid-standalone/_images/alerts-history.png)

  Figure 4. The arrow shows the alert history in the details pane.

### Servers, Server Groups, and Clusters Alert Views

View alerts associated with specific servers, server groups, or clusters:

1.  In the **Servers** list, click the **Status** column for your target server, server group, or
    cluster.

2.  Click the **View Associated Alerts** link in the details pane:

    ![View Associated Alerts link in the details pane](/mulesoft/current/en-us/hybrid-standalone/_images/alerts-view-details-pane.png)

    Figure 5. The arrow shows the **View Associated Alerts** link in the details pane.

### Alert History by Servers, Server Groups, and Clusters

Review historical alert activity for specific servers, server groups, or clusters:

1.  In the **Servers** list, click the name of your server, server group, or cluster.

2.  Click **Settings** in the navigation pane.

3.  Click the **Alerts History** tab:

    ![Alerts History tab on the Settings page](/mulesoft/current/en-us/hybrid-standalone/_images/alerts-settings-alerts-history-tab.png)

    Figure 6. The arrow shows the **Alerts History** tab on the **Settings** page.

## Manage Alerts

Efficiently manage your alert configurations through Runtime Manager’s alert management interface.

### Alert Management Operations

From the **Alerts** page, select one or more alerts and use the management controls:

![Select toggle, alert state switch, Duplicate icon, and Delete icon](/mulesoft/current/en-us/hybrid-standalone/_images/alerts-multi-select-manage.png)

Figure 7. The screenshot shows (**1**) the select toggle, (**2**) the alert state switch, (**3**)
the **Duplicate** icon, and (**4**) the **Delete** icon.

#### Enable and Disable Alerts

Control alert notification delivery for infrastructure monitoring:

- **Disable alerts**: Click the toggle switch to turn off notifications:

  ![Alert switch on](/mulesoft/current/en-us/hybrid-standalone/_images/alerts-switch-on.png)

  Figure 8. The arrow shows the alert switch on.

  The **Active** column changes from **Yes** to **No**.

- **Enable alerts**: Click the toggle switch to turn on notifications:

  ![Alert switch off](/mulesoft/current/en-us/hybrid-standalone/_images/alerts-switch-off.png)

  Figure 9. The arrow shows the alert switch off.

  The **Active** column changes from **No** to **Yes**.

> [!NOTE] Alert state changes affect all recipients of the alert notifications.

#### Duplicate Alerts

Create copies of existing alert configurations for similar infrastructure components:

1.  Select one or more alerts from the list.

2.  Click the **Duplicate** icon in the details pane:

    ![Duplicate alert icon](/mulesoft/current/en-us/hybrid-standalone/_images/alerts-duplicate.png)

    Figure 10. The arrow shows the **Duplicate** alert icon.

Runtime Manager creates alert copies with `-copy` appended to the original alert names.

#### Delete Alerts

Remove unnecessary alert configurations:

1.  Select one or more alerts from the list.

2.  Click the **Delete** (trash can) icon in the details pane:

    ![Delete (trash can) icon](/mulesoft/current/en-us/hybrid-standalone/_images/alerts-delete.png)

    Figure 11. The arrow shows the **Delete** alert (trash can) icon.

3.  Click **OK**.

## See Also

- [Monitoring Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/monitoring-hybrid-standalone)

- [Monitoring Dashboards for Server, Server Groups and Clusters](https://docs.mulesoft.com/hybrid-standalone/monitoring-dashboards-hybrid)

- [Getting Alerts](https://docs.mulesoft.com/monitoring/alerts-hf)

- [Features Supported on Hyperforce](https://docs.mulesoft.com/hyperforce/#features-supported-on-hyperforce)

- [Managing Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/managing-hybrid-standalone)