# mulesoft Hybrid Standalone Runtimes - Full Documentation

<!-- document id=bf0f22309c60247f59b2d26109667ef011dd0b1f069b5601b64563e93e18888b url=/mulesoft/current/en-us/hybrid-standalone/configure-ports-ips.md -->

---
product: Hybrid Standalone Runtimes
---

# Adding Ports, IPs, and Hostnames for Runtime Manager Agent

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

Configure network access for the Runtime Manager agent to establish secure communication between
your hybrid standalone instances and Anypoint Platform services.

## Overview

To enable Runtime Manager agent connectivity in your customer-hosted Mule runtime environment, you
must configure your network infrastructure to allow communication with Anypoint Platform APIs and
services. This configuration involves adding specific hostnames, ports, and IP addresses to your
network allowlists and firewall rules.

These sections provide the specific network configuration details required for each communication
protocol and regional deployment.

All connectivity requirements are for outbound connections from your network to Anypoint Platform.
No inbound connectivity to your network or servers is required.

Runtime Manager agent establishes persistent WebSocket connections that remain active for ongoing
communication with Anypoint Platform services.

This page lists US Cloud, EU Cloud, MuleSoft Government Cloud, Japan Cloud, India Cloud, Australia
Cloud, and United Kingdom Cloud endpoints. For Canada Cloud, allowlist the Platform URL, analytics
ingest, and Runtime Manager hosts in
[Control Plane Hostnames and Allowlists](https://docs.mulesoft.com/control-planes/control-plane-hostnames-allowlists).

## Mutual TLS Authentication Endpoints

The Runtime Manager agent uses mutual TLS (mTLS) to authenticate directly with these endpoints:

- runtime-manager.anypoint.mulesoft.com

- runtime-manager.eu1.anypoint.mulesoft.com

- runtime-manager.gov.anypoint.mulesoft.com

- runtime-manager.jp1.platform.mulesoft.com

- runtime-manager.in1.platform.mulesoft.com

- runtime-manager.au1.platform.mulesoft.com

- runtime-manager.gb1.platform.mulesoft.com

- data-authenticator.anypoint.mulesoft.com

- data-authenticator.gov.anypoint.mulesoft.com

- us1.ingest.mulesoft.com

- eu1.ingest.mulesoft.com

The `*.ingest.mulesoft.com` endpoints handle OpenTelemetry metrics ingestion.

> [!IMPORTANT] Configure your firewall or proxy to allow SSL passthrough for these endpoints. Don’t
> enable deep packet inspection (DPI) or SSL decryption. For `*.ingest.mulesoft.com`, allow outbound
> TCP on port 8443 and port 443.

## WebSocket Endpoints

These endpoints use WebSocket connections for real-time communication between the agent and Runtime
Manager. Ensure your firewall supports WebSocket protocol upgrades and persistent connections for
these endpoints.

- runtime-manager.anypoint.mulesoft.com

- runtime-manager.eu1.anypoint.mulesoft.com

- runtime-manager.gov.anypoint.mulesoft.com

- runtime-manager.jp1.platform.mulesoft.com

- runtime-manager.in1.platform.mulesoft.com

- runtime-manager.au1.platform.mulesoft.com

- runtime-manager.gb1.platform.mulesoft.com

## Required Ports and Hostnames

Configure your firewall to allow outbound connections to these ports and hostnames based on your
Anypoint Platform region.

<table><colgroup><col> <col> <col></colgroup><thead><tr><th>Region</th><th>Name</th><th>Port</th></tr></thead><tbody><tr><td><div><div><p><strong>US</strong></p></div></div></td><td><div><div><p>anypoint.mulesoft.com</p></div></div></td><td><div><div><p>443</p></div></div></td></tr><tr><td><div><div><p><strong>US</strong></p></div></div></td><td><div><div><p>runtime-manager.anypoint.mulesoft.com</p></div></div></td><td><div><div><p>443</p></div></div></td></tr><tr><td><div><div><p><strong>US</strong></p></div></div></td><td><div><div><p>analytics-ingest.anypoint.mulesoft.com</p></div></div></td><td><div><div><p>443</p></div></div></td></tr><tr><td><div><div><p><strong>US</strong></p></div></div></td><td><div><div><p>data-authenticator.anypoint.mulesoft.com</p></div></div></td><td><div><div><p>443</p></div></div></td></tr><tr><td><div><div><p><strong>US</strong></p></div></div></td><td><div><div><p>exchange-files.anypoint.mulesoft.com</p></div></div></td><td><div><div><p>443</p></div></div></td></tr><tr><td><div><div><p><strong>US</strong></p></div></div></td><td><div><div><p>exchange2-asset-manager-kprod.s3.amazonaws.com</p></div></div></td><td><div><div><p>443</p></div></div></td></tr><tr><td><div><div><p><strong>US</strong></p></div></div></td><td><div><div><p>us1.ingest.mulesoft.com</p></div></div></td><td><div><div><p>8443</p></div></div></td></tr><tr><td><div><div><p><strong>US-GOV</strong></p></div></div></td><td><div><div><p>runtime-manager.gov.anypoint.mulesoft.com</p></div></div></td><td><div><div><p>443</p></div></div></td></tr><tr><td><div><div><p><strong>US-GOV</strong></p></div></div></td><td><div><div><p>data-authenticator.gov.anypoint.mulesoft.com</p></div></div></td><td><div><div><p>443</p></div></div></td></tr><tr><td><div><div><p><strong>US-GOV</strong></p></div></div></td><td><div><div><p>gov.anypoint.mulesoft.com</p></div></div></td><td><div><div><p>443</p></div></div></td></tr><tr><td><div><div><p><strong>US-GOV</strong></p></div></div></td><td><div><div><p>exchange-files.gov.anypoint.mulesoft.com</p></div></div></td><td><div><div><p>443</p></div></div></td></tr><tr><td><div><div><p><strong>US-GOV</strong></p></div></div></td><td><div><div><p>exchange2-asset-manager-kgprod.s3.us-gov-west-1.amazonaws.com</p></div></div></td><td><div><div><p>443</p></div></div></td></tr><tr><td><div><div><p><strong>EU</strong></p></div></div></td><td><div><div><p>eu1.anypoint.mulesoft.com</p></div></div></td><td><div><div><p>443</p></div></div></td></tr><tr><td><div><div><p><strong>EU</strong></p></div></div></td><td><div><div><p>runtime-manager.eu1.anypoint.mulesoft.com</p></div></div></td><td><div><div><p>443</p></div></div></td></tr><tr><td><div><div><p><strong>EU</strong></p></div></div></td><td><div><div><p>analytics-ingest.eu1.anypoint.mulesoft.com</p></div></div></td><td><div><div><p>443</p></div></div></td></tr><tr><td><div><div><p><strong>EU</strong></p></div></div></td><td><div><div><p>data-authenticator.eu1.anypoint.mulesoft.com</p></div></div></td><td><div><div><p>443</p></div></div></td></tr><tr><td><div><div><p><strong>EU</strong></p></div></div></td><td><div><div><p>exchange2-asset-manager-kprod-eu.s3.eu-central-1.amazonaws.com</p></div></div></td><td><div><div><p>443</p></div></div></td></tr><tr><td><div><div><p><strong>EU</strong></p></div></div></td><td><div><div><p>eu1.ingest.mulesoft.com</p></div></div></td><td><div><div><p>8443</p></div></div></td></tr><tr><td><div><div><p><strong>JP</strong></p></div></div></td><td><div><div><p>runtime-manager.jp1.platform.mulesoft.com</p></div></div></td><td><div><div><p>8443</p></div></div></td></tr><tr><td><div><div><p><strong>IN</strong></p></div></div></td><td><div><div><p>runtime-manager.in1.platform.mulesoft.com</p></div></div></td><td><div><div><p>8443</p></div></div></td></tr><tr><td><div><div><p><strong>AU</strong></p></div></div></td><td><div><div><p>runtime-manager.au1.platform.mulesoft.com</p></div></div></td><td><div><div><p>8443</p></div></div></td></tr><tr><td><div><div><p><strong>GB</strong></p></div></div></td><td><div><div><p>runtime-manager.gb1.platform.mulesoft.com</p></div></div></td><td><div><div><p>8443</p></div></div></td></tr></tbody></table>

## Static IP Addresses

For network environments that require IP-based firewall rules, use these static IP addresses to
allow Runtime Manager connectivity.

- Allowlist these static IPs in the `US` region to access the `runtime-manager` hosts:

  <table><colgroup><col> <col> <col></colgroup><thead><tr><th>Region</th><th>Name</th><th>IP Address</th></tr></thead><tbody><tr><td><div><div><p><strong>US</strong></p></div></div></td><td><div><div><p>runtime-manager.anypoint.mulesoft.com</p></div></div></td><td><div><div><p>18.214.68.14</p></div></div></td></tr><tr><td><div><div><p><strong>US</strong></p></div></div></td><td><div><div><p>runtime-manager.anypoint.mulesoft.com</p></div></div></td><td><div><div><p>35.174.151.175</p></div></div></td></tr><tr><td><div><div><p><strong>US</strong></p></div></div></td><td><div><div><p>runtime-manager.anypoint.mulesoft.com</p></div></div></td><td><div><div><p>18.213.137.40 (Starting Feb 2024)</p></div></div></td></tr><tr><td><div><div><p><strong>US</strong></p></div></div></td><td><div><div><p>runtime-manager.anypoint.mulesoft.com</p></div></div></td><td><div><div><p>34.232.255.44 (Starting Feb 2024)</p></div></div></td></tr><tr><td><div><div><p><strong>US</strong></p></div></div></td><td><div><div><p>runtime-manager.anypoint.mulesoft.com</p></div></div></td><td><div><div><p>44.209.29.79 (Starting Feb 2024)</p></div></div></td></tr></tbody></table>

- Allowlist these static IPs in the `EU` region to access the `runtime-manager` hosts:

  <table><colgroup><col> <col> <col></colgroup><thead><tr><th>Region</th><th>Name</th><th>IP Address</th></tr></thead><tbody><tr><td><div><div><p><strong>EU</strong></p></div></div></td><td><div><div><p>runtime-manager.eu1.anypoint.mulesoft.com</p></div></div></td><td><div><div><p>18.185.141.77</p></div></div></td></tr><tr><td><div><div><p><strong>EU</strong></p></div></div></td><td><div><div><p>runtime-manager.eu1.anypoint.mulesoft.com</p></div></div></td><td><div><div><p>3.123.216.217</p></div></div></td></tr><tr><td><div><div><p><strong>EU</strong></p></div></div></td><td><div><div><p>runtime-manager.eu1.anypoint.mulesoft.com</p></div></div></td><td><div><div><p>3.127.253.183 (Starting Feb 2024)</p></div></div></td></tr></tbody></table>

> [!NOTE] Static IP addresses aren’t available for the Runtime Manager hosts in Japan Cloud, India
> Cloud, Australia Cloud, and United Kingdom Cloud. For these clouds, configure firewall rules using
> the hostnames in [Layer 7 Firewall Configuration](#layer-7-firewall-configuration).

## Dynamic IP Addresses

Configure hostname-based firewall rules for Anypoint Platform services that use dynamically assigned
IP addresses.

### Layer 7 Firewall Configuration

Some Anypoint Platform services use IP addresses that are dynamically assigned by cloud
infrastructure. For these services, configure Layer 7 firewall rules based on fully qualified domain
names (FQDNs) rather than static IP addresses.

Configure your Layer 7 firewall rules to include these hostnames:

<table><colgroup><col> <col></colgroup><thead><tr><th>Region</th><th>Hostname</th></tr></thead><tbody><tr><td><div><div><p><strong>US</strong></p></div></div></td><td><div><div><p>anypoint.mulesoft.com</p></div></div></td></tr><tr><td><div><div><p><strong>US</strong></p></div></div></td><td><div><div><p>analytics-ingest.anypoint.mulesoft.com</p></div></div></td></tr><tr><td><div><div><p><strong>US</strong></p></div></div></td><td><div><div><p>data-authenticator.anypoint.mulesoft.com</p></div></div></td></tr><tr><td><div><div><p><strong>US</strong></p></div></div></td><td><div><div><p>us1.ingest.mulesoft.com</p></div></div></td></tr><tr><td><div><div><p><strong>US-GOV</strong></p></div></div></td><td><div><div><p>runtime-manager.gov.anypoint.mulesoft.com</p></div></div></td></tr><tr><td><div><div><p><strong>US-GOV</strong></p></div></div></td><td><div><div><p>data-authenticator.gov.anypoint.mulesoft.com</p></div></div></td></tr><tr><td><div><div><p><strong>US-GOV</strong></p></div></div></td><td><div><div><p>gov.anypoint.mulesoft.com</p></div></div></td></tr><tr><td><div><div><p><strong>EU</strong></p></div></div></td><td><div><div><p>eu1.anypoint.mulesoft.com</p></div></div></td></tr><tr><td><div><div><p><strong>EU</strong></p></div></div></td><td><div><div><p>analytics-ingest.eu1.anypoint.mulesoft.com</p></div></div></td></tr><tr><td><div><div><p><strong>EU</strong></p></div></div></td><td><div><div><p>data-authenticator.eu1.anypoint.mulesoft.com</p></div></div></td></tr><tr><td><div><div><p><strong>EU</strong></p></div></div></td><td><div><div><p>eu1.ingest.mulesoft.com</p></div></div></td></tr><tr><td><div><div><p><strong>JP</strong></p></div></div></td><td><div><div><p>runtime-manager.jp1.platform.mulesoft.com</p></div></div></td></tr><tr><td><div><div><p><strong>IN</strong></p></div></div></td><td><div><div><p>runtime-manager.in1.platform.mulesoft.com</p></div></div></td></tr><tr><td><div><div><p><strong>AU</strong></p></div></div></td><td><div><div><p>runtime-manager.au1.platform.mulesoft.com</p></div></div></td></tr><tr><td><div><div><p><strong>GB</strong></p></div></div></td><td><div><div><p>runtime-manager.gb1.platform.mulesoft.com</p></div></div></td></tr></tbody></table>

### Agent-Specific Allowlist

Configure these URLs for Runtime Manager agent connectivity based on your agent version.

**Agent Version Requirements**

- **Mule 4.x**: Runtime Manager agent 2.2.0 or later

- **OpenTelemetry metrics ingestion**: Runtime Manager agent 2.7.0 or later

<table><colgroup><col> <col></colgroup><thead><tr><th>URL</th><th>Description</th></tr></thead><tbody><tr><td><div><div><p>runtime-manager.anypoint.mulesoft.com</p></div></div></td><td><div><div><p>ARM management capabilities (<strong>public-cert agents</strong>)</p></div></div></td></tr><tr><td><div><div><p>data-authenticator.anypoint.mulesoft.com</p></div></div></td><td><div><div><p>Metrics ingestion for arm-monitoring stack (<strong>public-cert agents</strong>)</p></div></div></td></tr><tr><td><div><div><p>us1.ingest.mulesoft.com (port 8443)</p></div></div></td><td><div><div><p>OpenTelemetry metrics ingestion (agent 2.7.0+)</p></div></div></td></tr><tr><td><div><div><p>eu1.ingest.mulesoft.com (port 8443)</p></div></div></td><td><div><div><p>OpenTelemetry metrics ingestion (agent 2.7.0+)</p></div></div></td></tr></tbody></table>

## See Also

- [Control Plane Hostnames and Allowlists](https://docs.mulesoft.com/control-planes/control-plane-hostnames-allowlists)

- [Setting up Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/setting-hybrid-standalone)

- [Creating Servers](https://docs.mulesoft.com/hybrid-standalone/creating-servers)

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

- [Deploying Mule Apps to Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/deploying-apps-hybrid-standalone)

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

<!-- document id=67d273108c524d507c6d27460910478efc9ce97447f85ab945ef3833833360c8 url=/mulesoft/current/en-us/hybrid-standalone/creating-alerts-hybrid-apps.md -->

---
product: Hybrid Standalone Runtimes
---

# Creating Alerts for Mule Apps Deployed to Hybrid Standalone

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

Configure proactive monitoring alerts for your Mule applications deployed to hybrid standalone
instances to ensure optimal performance, detect issues early, and maintain application reliability
across your distributed integration environment.

## Overview

Runtime Manager alerts for applications deployed to hybrid standalone are event alerts, such as
deployment success, deployment failure, and application undeployed.

Application performance monitoring based on metrics, such as response time, throughput, and resource
usage, isn’t available as Runtime Manager alerts. Use Anypoint Monitoring for those alerts. See
[Getting Alerts](https://docs.mulesoft.com/monitoring/alerts-hf).

On US Cloud and EU Cloud, Runtime Manager also provides threshold conditions for number of errors,
number of Mule messages, and response time.

> [!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, 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.

You can also create custom alerts for applications deployed to CloudHub and CloudHub 2.0.

CloudHub triggers custom alerts when your application sends notifications to the Runtime Manager
console using Anypoint Connector for CloudHub (CloudHub Connector). See
[Custom Application Alerts and Notifications](https://docs.mulesoft.com/cloudhub/custom-application-alerts) for
information.

For applications deployed to CloudHub 2.0, custom alerts indicate whether an app deploys
successfully and whether it’s behaving as expected. See
[Configuring Application Alerts](https://docs.mulesoft.com/cloudhub-2/ch2-config-app-alerts) for more information.

> [!NOTE] For CloudHub 2.0, Alerts apply to applications only, not servers.

## Rate Limits on Alerts

Anypoint Platform enforces rate limits to control alert frequency and prevent excessive email
notifications. There’s no defined limit to the number of Runtime Manager alerts.

## Create an Alert

Configure alerts to monitor your Mule applications 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: applications

    - **Application type**

      When the source is **Applications**, applications deploy to either CloudHub or local servers.
      Runtime Fabric application alerts are supported only using Anypoint Monitoring.

      You can’t create an alert that applies to both applications deployed to CloudHub and local
      servers. You must create separate alerts for each deployment type.

    - **Applications**

      The application to apply the alert to

    - **Condition**

      The condition that triggers the alert

      The available options depend on whether your alert is linked to an application running on
      CloudHub, or an application running locally. 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 application monitoring
requirements. Alert conditions range from simple status notifications to complex performance
threshold monitoring.

### Conditions for Applications Deployed to CloudHub

For applications deployed to CloudHub, these alert conditions apply:

CPU usage - CloudHub

The CPU usage of the CloudHub workers that run the application is above or below the percentage for
the specified period of time.

![CPU usage - Cloudhub](/mulesoft/current/en-us/hybrid-standalone/_images/alerts-conditions-apps-cpu.png)

To enable this condition, specify the percentage and duration that triggers the alert.

Custom application alert

The custom notification contains the specified text.

![Custom application alerts](/mulesoft/current/en-us/hybrid-standalone/_images/alerts-conditions-custom.png)

To enable this condition, specify the notification text from the CloudHub Connector in your Mule
application. When the text in one of the notifications matches the specified string, an alert is
sent.

Exceeds event traffic threshold

The number of events of any type exceeds the threshold for the specified period of time.

![Exceeds event traffic threshold](/mulesoft/current/en-us/hybrid-standalone/_images/alerts-conditions-exceeds-traffic.png)

To enable this condition, specify the capacity threshold and duration that triggers the alert. This
alert condition depends on the events you are tracking in your application. For information, see
[Business Events](https://docs.mulesoft.com/mule-runtime/latest/business-events).

Memory usage - CloudHub

Memory usage is a percentage that represents the JVM heap-used/JVM total memory. The alert triggers
if the memory usage is above or below the limit for the specified period of time.

![Memory usage - Cloudhub](/mulesoft/current/en-us/hybrid-standalone/_images/alerts-conditions-apps-memory.png)

To enable this condition, specify the percentage and duration that triggers the alert.

These alerts for applications deployed to CloudHub require no additional parameters:

- Deployment failed

- Deployment success

- Secure data gateway connected

- Secure data gateway disconnected

- Worker not responding

### Conditions for Applications Deployed to Local Servers

These threshold conditions apply 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.

For applications deployed to local servers, these alert conditions apply:

Number of errors

The number of messaging errors reported by Mule runtime server in one minute reaches the specified
limit. The number of errors reported depends on error handling configuration in the app. For
information about Mule errors, see [Mule Errors](https://docs.mulesoft.com/mule-runtime/latest/mule-error-concept).

![Number of errors](/mulesoft/current/en-us/hybrid-standalone/_images/alerts-conditions-number-errors.png)

To enable this condition, specify the number of errors per minute that triggers the alert.

Number of Mule messages

The number of Mule messages since the application started reaches the specified limit.

![Number of Mule messages](/mulesoft/current/en-us/hybrid-standalone/_images/alerts-conditions-number-mule-messages.png)

To enable this condition, specify the number of Mule messages that triggers the alert.

Response time

The response time reaches the specified limit.

![Response time](/mulesoft/current/en-us/hybrid-standalone/_images/alerts-conditions-response-time.png)

To enable this condition, specify the maximum response time that triggers the alert.

These event alerts for applications deployed to local servers require no additional parameters. They
are available on all control planes that support hybrid standalone:

- Application undeployed

- Deployment failure

- Deployment success

## 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. Application Alert Variables</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>CloudHub App Alerts</p></div></div></td><td><div><div><p><strong>CPU usage - CloudHub</strong></p></div></div></td><td rowspan="2"><div><div><p><code>${operator}</code> <code>${value}</code></p></div></div></td></tr><tr><td><div><div><p><strong>Memory usage - CloudHub</strong></p></div></div></td></tr><tr><td><div><div><p><strong>Custom application notification</strong></p></div></div></td><td><div><div><p><code>${user}</code> <code>${priority}</code> <code>${transactionId}</code> <code>${message}</code></p></div></div></td></tr><tr><td><div><div><p><strong>Deployment failed</strong></p></div></div></td><td><div><div><p><code>${user}</code> <code>${message}</code></p></div></div></td></tr><tr><td><div><div><p><strong>Deployment success</strong></p></div></div></td><td rowspan="2"><div><div><p><code>${user}</code></p></div></div></td></tr><tr><td><div><div><p><strong>Worker not responding</strong></p></div></div></td></tr><tr><td><div><div><p><strong>Exceeds event traffic threshold</strong></p></div></div></td><td><div><div><p><code>${period}</code> <code>${periodTimeUnit}</code></p></div></div></td></tr><tr><td rowspan="4"><div><div><p>Hybrid App Alerts</p></div></div></td><td><div><div><p>All Hybrid App Alerts</p></div></div></td><td><div><div><p><code>${name}</code></p></div></div></td></tr><tr><td><div><div><p><strong>Number of Mule messages</strong></p></div></div></td><td rowspan="3"><div><div><p><code>${currentValue}</code> <code>${threshold}</code> <code>${location}</code></p></div></div></td></tr><tr><td><div><div><p><strong>Number of errors</strong></p></div></div></td></tr><tr><td><div><div><p><strong>Response time</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>${currentValue}</code></p></td><td><p>Current value of metric that triggers the alert</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>${message}</code></p></td><td><p>Message from the notification that trigger the alert</p></td></tr><tr><td><p><code>${name}</code></p></td><td><div><div><p>Name of the app that triggers the alert</p></div></div></td></tr><tr><td><p><code>${operator}</code></p></td><td><p>An operator, such as <code>&lt; &gt; =</code></p></td></tr><tr><td><p><code>${period}</code></p></td><td><p>Period of time over which to measure</p></td></tr><tr><td><p><code>${periodTimeUnit}</code></p></td><td><p>Period of time unit</p></td></tr><tr><td><p><code>${priority}</code></p></td><td><p>Priority of the notification that triggers the alert</p></td></tr><tr><td><p><code>${resource}</code></p></td><td><div><div><p>Name of the app that triggers the alert</p></div></div></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><tr><td><p><code>${transactionId}</code></p></td><td><p>Transaction ID defined in the app or assigned by Mule</p></td></tr><tr><td><p><code>${user}</code></p></td><td><p>Anypoint Platform organization name</p></td></tr><tr><td><p><code>${value}</code></p></td><td><p>A value associated with an element</p></td></tr></tbody></table>

## Access and View Alerts

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

### Global Alert Management

Access all application alerts from the main alerts dashboard:

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

    ![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 application 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.

### Application-Specific Alert Views

View alerts associated with specific applications:

1.  In the **Applications** list, click the **Status** column for your target application.

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 Application

Review historical alert activity for specific applications:

1.  In the **Applications** list, click the name of your application.

2.  Click **Settings**.

3.  Click **Alerts History** :

    ![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 application 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 application 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 applications:

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)

- [Creating Alerts for Servers, Server Groups, and Clusters](https://docs.mulesoft.com/hybrid-standalone/creating-alerts-hybrid)

- [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)

<!-- document id=ce4ef14951d5799743c3a96b2aa92d99ce2ffa0be5f077bd847f18f505c50781 url=/mulesoft/current/en-us/hybrid-standalone/creating-alerts-hybrid.md -->

---
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)

<!-- document id=9819659911bf36d9f8950c8e48fb291fcfbd1ec55e17bcb7f82ba06228fafbd6 url=/mulesoft/current/en-us/hybrid-standalone/creating-clusters.md -->

---
product: Hybrid Standalone Runtimes
---

# Creating Clusters

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

Creating clusters enables high availability and load distribution across multiple Mule runtime
instances in your hybrid standalone environment.

## Understanding Clusters

A cluster is a set of up to eight servers that work together as a single deployment target with high
availability. Unlike server groups where applications run independently, cluster nodes communicate
with each other and share information.

Key characteristics of clusters:

- Application instances know about each other and share common information

- Nodes coordinate and synchronize their statuses across the cluster

- If one server fails, another server automatically takes over processing

- A single cluster can run multiple applications simultaneously

- Provides continuous service even when individual nodes fail

## Understanding Shared Memory in Clusters

Clusters use distributed shared memory grids to enable data sharing and coordination between cluster
nodes. This shared memory system allows applications to maintain state and share information across
all nodes in the cluster.

### How Shared Memory Works

The distributed shared memory grid enables:

- Data is automatically replicated across all cluster nodes

- Uses in-memory distributed storage for optimal performance

- Changes are automatically synchronized across all nodes

- Data remains available even if individual nodes fail

### Shared Memory Components

The shared memory grid manages several key components:

- Object Stores

  - Persistent and non-persistent Object stores are replicated across the cluster.

  - Data survives application redeploys and individual node restarts.

  - Maintains consistency across all cluster nodes.

- VM Queues

  - Persistent and transient VM queues are shared across the cluster

  - Messages can be processed by any available node

  - Ensures message delivery even during node failures

- Lock Factory

  - Distributed locking mechanism for cluster coordination

  - Prevents race conditions in multi-node environments

  - Manages concurrent access to shared resources

### Memory vs Database Storage

- Memory-Based Storage (Recommended)

  - Fastest access times with in-memory operations

  - Automatically scales with cluster size

  - No external database configuration required

- Built-in replication and synchronization

- Database-Based Storage (Alternative)

  - Data survives complete cluster shutdown

  - Requires JDBC database configuration

  - Slower than memory-based storage

  - Additional configuration and maintenance

### Performance Considerations

- Memory-Based Storage Benefits:

  - Optimal performance for most use cases

  - Automatic load distribution across nodes

  - Built-in high availability features

  - No external database dependencies

- When to Use Database Storage:

  - Long-term data persistence requirements

  - Compliance with data retention policies

  - Integration with existing database infrastructure

  - Audit and logging requirements

### Configuration Options

- Default Memory Grid Configuration

  - Automatic replication across all nodes

  - In-memory storage for optimal performance

  - Built-in failover and recovery mechanisms

- Custom Database Configuration

  - Configure Object Store to use JDBC-based storage

  - Requires external database setup and maintenance

  - Provides persistent storage beyond cluster lifecycle

> [!NOTE] For most hybrid standalone deployments, memory-based shared storage provides the best
> balance of performance, simplicity, and reliability. Use database-based storage only when
> long-term persistence is required beyond cluster restarts.

## Understanding Multicast vs Unicast Clusters

Choose between two cluster discovery methods based on your network requirements:

### Unicast Clusters

- You must configure the IP addresses of all nodes in the cluster

- Configure the internal IP that allows direct communication between nodes

- Cannot use DHCP for dynamic IP assignment since Mule identifies servers by IP address

- Servers must have Running status to join a unicast cluster

- When you add a server to a unicast cluster, all existing servers in the cluster are restarted

- Clustering across availability zones or regions can cause performance issues due to network
  latency

- Place all nodes on one subnet or availability zone to reduce performance risks

- If a server restarts with a new IP address, you must manually add it back to the cluster

### Multicast Clusters

- Servers discover each other without manual IP configuration

- All servers must be on the same network segment to communicate

- Server status doesn’t need to be Running to configure as a cluster node

- You can add nodes to the cluster without restarting the entire cluster

- Many networks block multicast functionality, so check with your network administrator

- Reduce configuration overhead compared to unicast clusters

## Before You Begin

Before creating clusters, make sure you have:

- At least one Mule server added to Runtime Manager (add servers first, then create the cluster to
  deploy applications)

- Network connectivity between all cluster nodes

- Proper firewall configuration for cluster communication

- Sufficient resources on each node

Additionally, review these limitations:

- Servers can’t contain any previously deployed applications.

- Servers can’t belong to another cluster or group.

- Multicast servers can be in the **Running** or **Disconnected** state.

- Unicast servers must be in the Running state.

- All servers in a cluster must be running the same Mule runtime engine version (including monthly
  update) and Runtime Manager agent version.

## Creating a Cluster

To create a new cluster:

1.  From Anypoint Platform, select **Runtime Manager**.

2.  Select **Servers**.

3.  Click **Create Cluster**:

    ![Create Cluster button](/mulesoft/current/en-us/hybrid-standalone/_images/rtm-cluster-create.png)

    Figure 1. The arrow shows the **Create Cluster** button on the **Servers** page.

4.  In the **Create Cluster** page, enter the name for the cluster.

    Cluster names can contain between 3-40 alphanumeric characters (a-z, A-Z, 0-9) and hyphens (-).
    They can’t start or end with a hyphen and can’t contain spaces or other characters.

5.  Select **Unicast** or **Multicast**.

6.  Select the servers to include in your new cluster.

7.  Click **Create Cluster**.

    - The new cluster appears in the **Servers** list.

    - The servers no longer appear in the **Servers** list.

To see the list of servers in the cluster, select the cluster name.

> [!NOTE] For Object Store persistence on all the servers in your cluster, create your cluster
> manually and use Quorum Management.

## Next Steps

After creating clusters, you can:

- Deploy applications with high availability

- Configure cluster-wide monitoring

- Set up automated scaling policies

## See Also

- [Creating Servers](https://docs.mulesoft.com/hybrid-standalone/creating-servers)

- [Creating Server Groups](https://docs.mulesoft.com/hybrid-standalone/creating-servers-groups)

- [Managing Clusters](https://docs.mulesoft.com/hybrid-standalone/managing-clusters)

<!-- document id=9b2bc9c85f4a1aee352700ce7af4c1a7a5bc7e64dba0abd6095f5fb41f7dd002 url=/mulesoft/current/en-us/hybrid-standalone/creating-servers-groups.md -->

---
product: Hybrid Standalone Runtimes
---

# Creating Server Groups

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

Create server groups to organize your hybrid standalone servers for easier management and
deployment.

A server group is a set of servers that act as a single deployment target for applications so that
you don’t have to deploy applications to each server individually.

## Understanding Server Groups

Deploying applications to servers in server groups provides redundancy so you can restore
applications more seamlessly and quickly, with less downtime.

Unlike clusters, application instances in a server group run in isolation from the application
instances running on the other servers in the group. If you experience concurrency issues with
server groups, consider grouping servers in clusters.

### Understanding Server Groups and Mule Apps Behavior

When you deploy Mule applications to a server group, these behaviors apply:

#### Application Deployment and Updates

- When you add a Mule application to a server group, it deploys to all servers in the group
  automatically.

- When you update a Mule application in a server group, the update applies to all servers in the
  group. Review these considerations for server updates:

  - Servers with `Unknown` status are not updated until they reconnect to the MuleSoft control
    plane.

  - You can only update a Mule application once if servers in the group have `Unknown` status.

  - If you update a Mule application (for example, from version 1 to version 2) while servers have
    `Unknown` status, you can’t perform additional updates (such as from version 2 to version 3)
    until you remove the unknown servers from the server group or start and reconnect the unknown
    servers to the control plane.

- When you delete a Mule application from a server group, it removes the application from all
  servers in the group.

#### Manual Application Management (Not Recommended)

Manually managing Mule applications directly on servers that belong to a server group is not
recommended and defeats the purpose of using server groups.

If you manually modify the applications directory (`apps`) on a server that belongs to a server
group, the following issues occur:

- Adding applications directly  
  If you manually add a `.jar` file to a server’s `apps` folder, the application deploys only to
  that specific server and becomes a rogue API that is not visible in Runtime Manager’s server group
  view and is not deployed to other servers in the group.

- Updating applications directly  
  If you manually update a Mule application by deleting the previous version and dropping a new
  `.jar` file, the same issues as adding applications directly apply.

- Deleting applications directly  
  If you manually delete a Mule application folder (including the anchor file), the API is deleted,
  but since you didn’t remove the application from the server group, it redeploys when you restart
  the server.

## Before You Begin

Before creating server groups, ensure that you have:

- At least one hybrid standalone server configured

- Appropriate permissions to create and manage server groups

- Access to Runtime Manager

## Requirements and Limitations

Additionally, review these requirements and limitations:

All servers in a server group must be running the same versions of:

- Mule runtime engine

- Runtime Manager agent

- Java

- You can create a server group with servers with the `Running` or the `Disconnected` status, but
  these can’t be in the same group as servers with the `Created` status.

- You can create a server group with servers with the `Created` status.

- To add a server on which existing applications are currently running to a server group, first stop
  and delete the applications from the server.

## Create a Server Group

When creating a server group, you can either:

- Add the servers to Runtime Manager first and then create the server group.

- Create the group and add servers to it later.

To create a server group:

1.  From Anypoint Platform, select **Runtime Manager**.

2.  Select **Servers**.

3.  Click **Create Group**.

4.  In the **Create Server Group** page, enter the name for the server group.

    Group names can contain between 3-40 alphanumeric characters (a-z, A-Z, 0-9) and hyphens (-).
    They can’t start or end with a hyphen, and they can’t contain spaces or other characters.

5.  Select the servers to include in your new server group.

6.  Click **Create Group**.

    - The new server group appears in the **Servers** list.

    - The servers no longer appear in the **Servers** list.

To see the list of servers in the group, select the server group name.

## Next Steps

After creating server groups, you can:

- Deploy applications to the entire group

- Configure monitoring and alerts at the group level

- Manage properties and settings across all servers in the group

## See Also

- [Creating Servers](https://docs.mulesoft.com/hybrid-standalone/creating-servers)

- [Managing Server Groups](https://docs.mulesoft.com/hybrid-standalone/managing-servers-groups)

- [Creating Clusters](https://docs.mulesoft.com/hybrid-standalone/creating-clusters)

<!-- document id=ede0d3ee6d1c2870ca377b94f5f062396abb6b4ad33f127e7c0ad4956f0914d5 url=/mulesoft/current/en-us/hybrid-standalone/creating-servers.md -->

---
product: Hybrid Standalone Runtimes
---

# Creating Servers

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

Create and manage individual Mule runtime engine instances (servers) through Anypoint Runtime
Manager to deploy and monitor your applications in hybrid standalone environments. Manage servers
either individually or in server groups or clusters.

## Understanding Servers

Servers communicate with Runtime Manager using the Runtime Manager agent. After creating a server,
use Runtime Manager to deploy applications to the Mule instance and view information about the
environment where you installed Mule.

For each Mule instance that you want to manage, add a server to Runtime Manager. In environments
with multiple Mule instances, use server groups and clusters for redundancy, high availability, and
ease of management.

## Before You Begin

Before adding a server to Runtime Manager:

- Have a current enterprise license.

- Run Mule 4.x or later.

- Install the Runtime Manager agent.

- Have an Enterprise support account if downloading the agent.

- Remove existing server registration if already registered in another Runtime Manager instance.

For details, refer to
[Install or Update the Runtime Manager agent](https://docs.mulesoft.com/runtime-manager/runtime-manager-agent).

## Create a Server

To create a server, add it to Runtime Manager:

1.  From Anypoint Platform, select **Runtime Manager**.

2.  Click **Servers** in the menu.

3.  Click the **Add Server** button.

4.  Enter a name for your server.

    Server names can contain up to 60 alphanumeric characters (a-z, A-Z, 0-9), periods (.), hyphens
    (-), and underscores (\_), but not spaces or other special characters. Runtime Manager supports
    Unicode characters in server names.

    The server name must be unique in the environment, but it can be the same for the same
    organization in different environments.

    Runtime Manager generates the `amc_setup` command. This command includes the server name you
    specified (`_server-name_`) and the registration token (`_token_`) required to register Mule in
    your environment. The registration token includes your organization ID and the current
    environment.

    ![amc\_setup command in the Add Server window](/mulesoft/current/en-us/hybrid-standalone/_images/rtm-add-server.png)

    Figure 1. The arrow shows the `amc_setup` command in the **Add Server** window.

5.  Click **Copy command** to copy the `amc_setup` command.

    This button appears only if the server name you specify is valid.

6.  In a terminal window, change to the `$MULE_HOME/bin` directory for the Mule instance that you’re
    registering.

7.  Paste the command on the command line.

8.  Include any other parameters on the `amc_setup` command line.

    For information, see
    [amc\_setup Parameters](https://docs.mulesoft.com/runtime-manager/installing-and-configuring-runtime-manager-agent#amc_setup-parameters).

9.  If your environment requires all outbound calls to go through a proxy, specify proxy settings in
    either the `$MULE_HOME/conf/mule-agent.yml` file or the `$MULE_HOME/conf/wrapper.conf` file.

    See [Connect the Agent Through a Proxy Server](https://docs.mulesoft.com/runtime-manager/rtm-agent-proxy-config).

When the `amc_setup` command completes successfully, you see:

Mule Agent configured successfully Connecting to Access Management to extract client\_id and
client\_secret Credentials extracted correctly, updating wrapper conf file

After the script completes successfully, the name of your server appears on the **Servers** tab of
Runtime Manager with a status of `Created`.

If the server was running when you ran the `amc_setup` script, restart the server to reconnect with
Runtime Manager.

## Remove a Server from Another Runtime Manager Instance

If the server you want to add is already registered with a different instance of Runtime Manager,
you must remove it before you can register the new one.

To remove the server:

1.  From Anypoint Platform, select **Runtime Manager**.

2.  Select **Servers**.

3.  Click the server name.

4.  Click **Settings**.

5.  From the **Actions** menu, select **Delete**.

6.  In the `$MULE_HOME/conf` directory, delete the `mule-agent.yaml` and `mule-agent.jks` files.

For details, refer to [Managing Servers](https://docs.mulesoft.com/hybrid-standalone/managing-servers).

## Next Steps

After creating servers, you can:

- Deploy applications to your servers

- Organize servers into groups or clusters for better management

- Configure monitoring and alerts for server health

- Set up properties and environment variables for your applications

## See Also

- [Setting up Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/setting-hybrid-standalone)

- [Creating Server Groups](https://docs.mulesoft.com/hybrid-standalone/creating-servers-groups)

- [Creating Clusters](https://docs.mulesoft.com/hybrid-standalone/creating-clusters)

- [Managing Servers](https://docs.mulesoft.com/hybrid-standalone/managing-servers)

- [Runtime Manager Agent](https://docs.mulesoft.com/runtime-manager/runtime-manager-agent)

<!-- document id=d837c3380e51c218a6a1f13cf46737a860aea94c073664b737c520f1c26346e4 url=/mulesoft/current/en-us/hybrid-standalone/deploying-apps-hybrid-standalone.md -->

---
product: Hybrid Standalone Runtimes
---

# Deploying Mule Apps to Hybrid Standalone Instances

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

Deploy your Mule applications to hybrid standalone instances for on-premises execution with
centralized cloud-based management, enabling secure integration within your infrastructure while
maintaining operational visibility and control.

## Overview

Key deployment capabilities include:

- Multi-target deployment: servers, server groups, and clusters

- Application source flexibility: Anypoint Exchange, local files, and environment promotion

- Configuration management: properties, logging, and monitoring settings

- Real-time deployment tracking and status monitoring

- Post-deployment management and update capabilities

## Deployment Targets

Select deployment targets based on your application’s availability requirements, load distribution
needs, and infrastructure architecture.

- Servers  
  Deploy to specific server instances for development, testing, or applications requiring dedicated
  resources.

- Server Groups  
  Deploy to multiple servers simultaneously for load distribution and horizontal scaling.

- Clusters  
  Deploy to high-availability clusters for mission-critical applications requiring fault tolerance.

### Deployment Methods

Choose from multiple deployment approaches based on your development workflow and integration
requirements:

- Runtime Manager Console  
  Web-based deployment through Anypoint Platform with visual deployment management

- Runtime Manager API  
  Programmatic deployment for CI/CD pipelines and automated workflows

- Maven Plugin  
  Integration with build processes for developer-centric deployment workflows

> [!IMPORTANT] When you use Runtime Manager to manage a server, you can’t use other deployment
> methods or tools to manage that server. This ensures consistent state management and prevents
> configuration conflicts.

## Before You Begin

Make sure your hybrid standalone environment meets the deployment requirements before initiating
application deployment.

Review [Requirements and Limitations](https://docs.mulesoft.com/hybrid-standalone/hybrid-standalone-requirements-limitations) to understand
deployment and server scaling limits and plan your infrastructure within platform constraints.

### Infrastructure Requirements

Complete this infrastructure setup:

1.  [Download, Install, Configure, and Upgrade On-Premises Mule Runtime Engine](https://docs.mulesoft.com/on-premises/latest/runtime-installation-task)
    on target servers with appropriate Java version compatibility

2.  [Add servers to Runtime Manager](https://docs.mulesoft.com/hybrid-standalone/creating-servers) for centralized management and deployment
    capabilities

3.  Ensure servers have connectivity to Anypoint Platform for management communication

### Environment Promotion Requirements

When promoting applications across environments (sandbox to production), verify these requirements:

- Valid permissions on both source and target environments for deployment operations

- Identical or compatible Mule runtime versions across environments to prevent deployment failures

- Matching deployment target types (server, server group, cluster) between source and destination

- All servers in clusters must use the same Java version that matches application requirements

> [!NOTE] You can verify Java version compatibility by checking server details in **Runtime
> Manager** > **Servers** before deployment.

### Application Compatibility

Verify your application meets these deployment criteria:

- Application built for target Mule runtime version

- All dependencies available in target environment

- Configuration properties aligned with target environment requirements

- Resource requirements compatible with target server capacity

## Deploy Applications Through Runtime Manager

Deploy Mule applications to your hybrid standalone infrastructure using Runtime Manager’s web
console for comprehensive deployment management and monitoring.

### Access the Deployment Interface

1.  Sign in to Anypoint Platform.

2.  Navigate to **Runtime Manager**.

3.  In the **Applications** page, click **Deploy application**.

### Configure Application Identity

- **Application Name**

Provide a unique application name that identifies your deployment across environments:

- 3-42 alphanumeric characters (a-z, A-Z, 0-9) and dashes (-) only

- Must be unique within the target environment (Runtime Manager validates automatically)

- Application names can’t be changed after deployment

> [!IMPORTANT] Choose meaningful application names that reflect functionality or environment for
> easier identification in operational dashboards. For example, `customer-api-prod` or
> `inventory-sync-dev`.

- **Deployment Target Selection**

Select your deployment target based on application requirements:

- Target must be in **Running** status to accept deployments

- Available options depend on your configured infrastructure (servers, server groups, clusters)

- Target selection determines available Mule runtime version for deployment

### Application Source Configuration

Choose your application source based on development workflow and artifact management practices:

- Exchange Integration

Deploy applications directly from Anypoint Exchange for centralized artifact management:

1.  Click **Choose file > Import file from Exchange**.

2.  Select **Application** as the asset type.

3.  Search for your application by name.

4.  Select the target application and choose the desired version.

5.  Click **Select**.

Benefits: Version control, dependency management, organizational sharing

- Local File Upload

Deploy applications from local development builds:

1.  Click **Choose file > Upload file**.

2.  Browse and select your application JAR file.

3.  Click **Open** to upload.

Best for: Development testing, custom builds, hotfixes

- Environment Promotion

Promote applications from non-production environments to maintain consistency:

1.  Click **Get from sandbox** (available when non-production environments exist).

2.  Select the source environment (for example, Sandbox, QA).

3.  Search and select the application to promote.

4.  Click **Apply**.

> [!NOTE] Only applications deployed to hybrid standalone infrastructure can be promoted to other
> hybrid deployments. CloudHub applications require separate CloudHub-to-CloudHub promotion.

### Deployment Configuration

Configure application settings through specialized configuration tabs before initiating deployment:

![Configuration tabs on the Deploy Application page](/mulesoft/current/en-us/hybrid-standalone/_images/rtm-deploy-to-own-servers.png)

Figure 1. The arrow shows the configuration tabs on the **Deploy Application** page.

**Deployment Target**

Verify runtime compatibility between your application and target infrastructure:

- Target selection automatically determines available Mule version

- Ensure this matches your application’s development runtime version

- Incompatible versions cause deployment failures

**Insights**

Configure application analytics and monitoring metadata:

- Enable tracking for business transaction monitoring

- Configure application-specific monitoring points

- Enable detailed transaction flow analysis

**Properties**

Define runtime properties that control application behavior:

- Configure environment-specific settings (endpoints, credentials, timeouts)

- Promoted applications retain original properties (editable before deployment)

- Use secure property management for sensitive configuration data

Property Management Resources:

- [Manage Properties for Applications On-Premises](https://docs.mulesoft.com/runtime-manager/hybrid-manage-props)

- [Safely Hide Application Properties](https://docs.mulesoft.com/cloudhub/secure-application-properties)

**Logging**

Set application-specific logging levels for operational visibility:

- `TRACE`, `DEBUG`, `INFO`, `WARN`, `ERROR`, `FATAL`

- Logging configuration overrides application defaults

- Modify `log4j2.xml` for advanced logging scenarios

For details, refer to:

- [Configuring Custom Logging Settings](https://docs.mulesoft.com/mule-runtime/latest/logging-in-mule#configuring-custom-logging-settings)

- [Apache Logging Services](https://logging.apache.org/log4j/2.x/manual/configuration.html)

### Execute Deployment

1.  Click **Deploy Application** to initiate the deployment process.

2.  Monitor deployment status in the Applications dashboard.

3.  Verify successful deployment through application status indicators.

The new application appears in the deployed applications list with a status indicator showing
deployment progress and final state.

## Update Deployed Applications

Perform application updates through Runtime Manager to deploy new versions or apply configuration
changes with minimal service disruption.

### Application Version Updates

Update application artifacts while preserving existing configuration:

1.  Navigate to **Applications** page and select your deployed application.

2.  Click **Choose File**.

3.  Select new application version through the same source options:

    - Exchange version update

    - Local file upload

    - Environment promotion

4.  Review configuration changes if needed.

5.  Click **Deploy Application**.

### Configuration Updates

Modify application properties and settings without changing the application artifact:

1.  Select the deployed application from the Applications list.

2.  Access configuration tabs (Properties, Logging, Insight).

3.  Make necessary configuration changes.

4.  Apply changes to trigger configuration reload.

### Troubleshoot Deployment Errors

Use these steps to troubleshoot deployment errors:

1.  Review status indicator and error messages in the Applications dashboard.

2.  Access detailed error information through the application’s log view.

3.  Confirm all deployment prerequisites are met (runtime version, connectivity, permissions).

4.  Validate application properties and external system connectivity.

5.  Correct identified issues and redeploy the application.

## See Also

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

- [Creating Servers](https://docs.mulesoft.com/hybrid-standalone/creating-servers)

- [Creating Server Groups](https://docs.mulesoft.com/hybrid-standalone/creating-servers-groups)

- [Creating Clusters](https://docs.mulesoft.com/hybrid-standalone/creating-clusters)

- [Monitoring Dashboards for Mule Apps Deployed to Hybrid Standalone](https://docs.mulesoft.com/hybrid-standalone/monitoring-dashboards-hybrid-apps)

- [Creating Alerts for Mule Apps Deployed to Hybrid Standalone](https://docs.mulesoft.com/hybrid-standalone/creating-alerts-hybrid-apps)

<!-- document id=855beb125e64fd8e4ded5bedc498d16f01fe304b584851b37c78b929c7a0aa81 url=/mulesoft/current/en-us/hybrid-standalone/hybrid-standalone-hadr.md -->

---
product: Hybrid Standalone Runtimes
---

# Hybrid Standalone High Availability and Disaster Recovery

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

Hybrid Standalone lets you host Mule runtime engine on servers or cloud instances that you control,
and manage them centrally through Anypoint Platform. You achieve high availability (HA) by
clustering multiple Mule runtime instances, so that another node takes over when one fails. You own
disaster recovery (DR) under a shared-responsibility model: because you control the infrastructure,
you back up, restore, and recover it with your own tooling, while MuleSoft provides HA best
practices and keeps the Anypoint Platform control plane available.

For an overview of HA and DR across all Mule deployment models, see
[High Availability and Disaster Recovery Across Deployment Models](https://docs.mulesoft.com/hosting-home/hadr-guide).

## High Availability Versus Disaster Recovery

High availability (HA) measures a system’s ability to remain accessible when a component fails. On
Hybrid Standalone, you achieve HA by clustering Mule runtime instances, so that another node takes
over when one fails.

Disaster recovery (DR) restores a system to an acceptable previous state after a natural or man-made
disaster, such as flooding, power failures, server failures, or misconfigurations.

Both strategies increase availability but differ in scope: on Hybrid Standalone, HA keeps your
application serving requests when a server in the cluster fails with no loss of service, whereas DR
restores service and data after an infrastructure disaster and usually incurs a brief loss of
service while the DR plan runs.

Two measurable objectives drive your DR plan:

Recovery Time Objective (RTO)

The maximum downtime a business tolerates. RTO is the time the system takes to recover after a
disruption.

Recovery Point Objective (RPO)

The maximum data loss a business accepts after a disaster. RPO drives how often you back up data.

## High Availability in Hybrid Standalone

You achieve high availability in Hybrid Standalone by grouping servers into a cluster.

Clustering

A cluster groups up to eight servers that act as a single deployment target. The nodes communicate,
coordinate their status, and share information. When one server fails, another server in the cluster
automatically takes over, which provides failover with no loss of service.

Shared memory

A cluster uses a distributed shared-memory grid that replicates data across nodes and keeps it
available when a node fails. The shared components include object stores, VM queues, and a
distributed lock factory. MuleSoft recommends memory-based storage for performance. Choose
database-based (JDBC) storage when you need persistence beyond the cluster lifecycle.

Node discovery

A cluster discovers nodes through one of two methods. With unicast, you configure the IP addresses
of the nodes, and adding a server restarts the cluster. With multicast, nodes discover each other
automatically, but many networks block multicast traffic.

To create and manage clusters, see [Creating Clusters](https://docs.mulesoft.com/hybrid-standalone/creating-clusters) and
[Managing Cluster](https://docs.mulesoft.com/hybrid-standalone/managing-clusters). For a deeper reference on Mule runtime clustering, see
[On-Premises Mule Runtime High Availability Cluster Overview](https://docs.mulesoft.com/on-premises/latest/mule-high-availability-ha-clusters).

## Disaster Recovery in Hybrid Standalone

Because you control the infrastructure in Hybrid Standalone, you and MuleSoft share disaster
recovery responsibilities.

Your responsibility

You back up and restore the runtime plane, fail over applications, and run DR procedures with your
own tooling and infrastructure. Align your cluster DR with standby-site strategies. Back up your
platform configurations, such as connections and properties, with the Anypoint CLI or Anypoint
Platform APIs.

MuleSoft responsibility

MuleSoft keeps the Anypoint Platform control plane available across multiple availability zones. The
control plane stores only operational metadata and configuration, not your business data. For a
full-region control-plane loss, MuleSoft maintains documented recovery objectives.

## Considerations and Limitations

Account for these factors when you design a clustered Hybrid Standalone topology:

Network topology

Clustering across availability zones or regions can degrade performance because of network latency.
Where possible, place cluster nodes on the same subnet or availability zone.

Simultaneous node restarts

Don’t restart multiple cluster nodes at the same time, such as during operating system patching.
Concurrent restarts can trigger cluster-membership eviction and distributed-lock partition
migration, which can take applications offline.

Cluster rejoin behavior

After a network interruption, evicted nodes might not rejoin the cluster automatically and can
require a manual restart. Account for this behavior in your operational runbooks.

Object Store persistence

Object Store persistence doesn’t support sharing the same database across different clusters. Plan
your persistence strategy accordingly.

Object Store locking

For Object Store lock handling in clusters, use an Object Store Connector version that supports
configurable lock timeouts, which prevents indefinite lock hangs.

## Best Practices

- Keep your integrations stateless, and externalize state to an external store, such as a database
  or a messaging queue.

- Run identical Mule runtime, Runtime Manager agent, and Java versions on all cluster nodes.

- Schedule cluster changes during maintenance windows.

- Test your failover and restore procedures regularly.

## See Also

- [High Availability and Disaster Recovery Across Deployment Models](https://docs.mulesoft.com/hosting-home/hadr-guide)

- [Creating Clusters](https://docs.mulesoft.com/hybrid-standalone/creating-clusters)

- [Managing Cluster](https://docs.mulesoft.com/hybrid-standalone/managing-clusters)

- [On-Premises Mule Runtime High Availability Cluster Overview](https://docs.mulesoft.com/on-premises/latest/mule-high-availability-ha-clusters)

<!-- document id=37393b41fbaf2bf50f755d678921ec4cfabccb09718aecc50f51ebbb93a9b830 url=/mulesoft/current/en-us/hybrid-standalone/hybrid-standalone-release-notes.md -->

---
product: Hybrid Standalone Runtimes
---

# Hybrid Standalone Release Notes

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

These are the release notes for Hybrid Standalone deployments.

## August 19, 2026

### What’s New

- Hybrid Standalone Mule (HSA) is now available in all control planes: US Cloud, Canada Cloud, EU
  Cloud, Japan Cloud, India Cloud, and Australia Cloud.

- Anypoint Monitoring adds support for Hybrid Standalone Deployments to more cloud control planes:

  - [Australia](https://au1.platform.mulesoft.com/monitoring) Cloud

  - [Canada](https://ca1.platform.mulesoft.com/monitoring) Cloud

  - [India](https://in1.platform.mulesoft.com/monitoring) Cloud

  - [Japan](https://jp1.platform.mulesoft.com/monitoring) Cloud

    For the required version of the Anypoint Monitoring agent installer and setup instructions,
    refer to
    [Anypoint Monitoring Release Notes](https://docs.mulesoft.com/release-notes/monitoring/anypoint-monitoring-installer-release-notes#august-19-2026).

## November 3, 2025

### What’s New

- Hybrid Standalone documentation is now available.  
  For more information, refer to [Hybrid Standalone](https://docs.mulesoft.com/hybrid-standalone/).

## See Also

- [Hybrid Standalone Runtimes Overview](https://docs.mulesoft.com/hybrid-standalone/)

- [Known Issues](https://help.salesforce.com/s/issues)

<!-- document id=ad9080c2da1f72ef7e0f0aa96d8172ad7d12c40c3c5834b117f0c86eaa51d427 url=/mulesoft/current/en-us/hybrid-standalone/index.md -->

---
product: Hybrid Standalone Runtimes
---

# Hybrid Standalone Runtimes Overview

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

Hybrid Standalone Runtimes are Mule runtime engines that you host in an environment you control and
register with Anypoint Runtime Manager. This option provides the control and security of deployments
within your trust boundary, plus centralized management from Anypoint Platform.

A hybrid standalone instance is one running copy of that runtime. Runtime Manager lists the instance
as a server. Setup, management, deployment, and monitoring topics use **instance** for that running
copy.

Mule can run on a physical server, a virtual machine, or a third-party cloud service such as Amazon
Web Services (AWS) or Microsoft Azure.

## Key Benefits

- Infrastructure control  
  Deploy on your own servers or cloud instances while maintaining full control over network security
  and meeting data residency requirements.

- Centralized management  
  Leverage Anypoint Platform for centralized application deployment, real-time monitoring, and
  unified dashboards across all deployments.

- Scalability  
  Scale horizontally by adding more servers, creating server groups for load distribution, and
  implementing clusters for high availability.

- Compliance and security  
  Meet regulatory compliance requirements and integrate seamlessly with existing infrastructure and
  monitoring tools.

- Hybrid flexibility  
  Combine the control and security of on-premises deployments with the flexibility and management
  capabilities of cloud-based services.

## Architecture Overview

Hybrid Standalone architecture consists of:

- Mule runtime engine  
  Runs on your infrastructure to execute applications and integrations.

- Runtime Manager agent  
  Connects your Mule instances to Anypoint Platform management plane.

- Anypoint Platform  
  Provides cloud-based services for application lifecycle management and observability.

- Anypoint Runtime Manager  
  Delivers the central interface for deploying and managing your applications.

## Use Cases

Hybrid Standalone is ideal for:

- Enterprise integration requiring connectivity between on-premises systems and cloud services.

- Regulatory compliance scenarios that maintain data residency requirements, audit trails, and
  industry-specific regulations within specific geographic boundaries.

- High-performance applications with low-latency processing requirements, high-throughput data
  processing, and direct database access needs.

- Legacy system integration and modernization efforts that enable gradual migration to cloud-based
  services while maintaining existing network configurations.

- Custom performance optimization scenarios that provide full control over infrastructure, network
  security policies, and direct system access.

## Get Started

Follow these steps to set up and deploy your hybrid standalone infrastructure:

1.  Review requirements and limitations

2.  Set up your infrastructure

3.  Register servers with Runtime Manager

4.  Deploy applications

5.  Manage your infrastructure

6.  Monitor and maintain

### Review Requirements and Limitations

Before you begin, understand the hardware, software, and licensing requirements for hybrid
standalone deployments:

- Review hardware specifications, operating system compatibility, and JDK requirements.

- Understand core-based licensing and infrastructure scaling limits.

- Plan network configuration and firewall requirements.

See [Requirements and Limitations](https://docs.mulesoft.com/hybrid-standalone/hybrid-standalone-requirements-limitations) for complete details.

### Set Up Your Infrastructure

Install and configure Mule runtime engine on your servers:

- Download and install Mule runtime engine on your target servers.

- Configure Runtime Manager agent for communication with Anypoint Platform.

- Set up network connectivity and configure firewall rules for required ports and IP addresses.

See [Setting up Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/setting-hybrid-standalone) and
[Adding Ports, IPs, and Hostnames for Runtime Manager Agent](https://docs.mulesoft.com/hybrid-standalone/configure-ports-ips) for setup
instructions.

### Register Servers with Runtime Manager

Create and register your servers, server groups, or clusters in Runtime Manager:

- [Create individual servers](https://docs.mulesoft.com/hybrid-standalone/creating-servers) for development, testing, or dedicated application
  deployments.

- [Create server groups](https://docs.mulesoft.com/hybrid-standalone/creating-servers-groups) for load distribution across multiple servers.

- [Create clusters](https://docs.mulesoft.com/hybrid-standalone/creating-clusters) for high-availability deployments with automatic failover.

Review [Requirements and Limitations](https://docs.mulesoft.com/hybrid-standalone/hybrid-standalone-requirements-limitations) to understand
deployment and server scaling limits and plan your infrastructure within platform constraints.

### Deploy Applications

Deploy your Mule applications to registered servers, server groups, or clusters:

- Deploy applications through Runtime Manager console, API, or Maven plugin.

- Configure application properties, logging levels, and monitoring settings.

- Manage application lifecycle including updates and redeployments.

See [Deploying Mule Apps to Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/deploying-apps-hybrid-standalone) for
deployment workflows.

### Manage Your Infrastructure

Perform ongoing management of your hybrid standalone environment:

- [Manage servers](https://docs.mulesoft.com/hybrid-standalone/managing-servers), [server groups](https://docs.mulesoft.com/hybrid-standalone/managing-servers-groups), and
  [clusters](https://docs.mulesoft.com/hybrid-standalone/managing-clusters).

- [Manage deployed applications](https://docs.mulesoft.com/hybrid-standalone/managing-apps-hybrid-standalone) including
  [properties](https://docs.mulesoft.com/hybrid-standalone/managing-properties-hybrid) and [schedulers](https://docs.mulesoft.com/hybrid-standalone/managing-schedulers-hybrid).

- Apply updates, scale infrastructure, and perform maintenance operations.

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

### Monitor and Maintain

Set up monitoring and alerting for servers and applications:

- Configure
  [monitoring dashboards for servers, server groups, and clusters](https://docs.mulesoft.com/hybrid-standalone/monitoring-dashboards-hybrid).

- Set up [alerts for infrastructure health and performance](https://docs.mulesoft.com/hybrid-standalone/creating-alerts-hybrid).

- Monitor [application-specific metrics](https://docs.mulesoft.com/hybrid-standalone/monitoring-dashboards-hybrid-apps) and configure
  [application alerts](https://docs.mulesoft.com/hybrid-standalone/creating-alerts-hybrid-apps).

See [Monitoring Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/monitoring-hybrid-standalone) and
[Monitoring Mule Apps](https://docs.mulesoft.com/hybrid-standalone/monitoring-apps-hybrid-standalone) for monitoring guidance.

## See Also

- [Setting up Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/setting-hybrid-standalone)

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

- [Deploying Mule Apps to Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/deploying-apps-hybrid-standalone)

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

<!-- document id=8e5ef466102f11b55b613fff75f4ac5ba69deaad24e37459a885e4334854cd5c url=/mulesoft/current/en-us/hybrid-standalone/managing-clusters.md -->

---
product: Hybrid Standalone Runtimes
---

# Managing Cluster

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

Managing clusters involves coordinating multiple Mule runtime instances working together to provide
high availability and load distribution.

## Add Servers to a Cluster

Add individual servers to an existing cluster to increase processing capacity and enhance high
availability across your deployment infrastructure.

Make sure that you follow these requirements:

- The target cluster already exists.

- At least one server is configured and available.

- All servers being added must run identical versions of:

  - Mule runtime

  - Runtime Manager agent

  - Java

> [!IMPORTANT] Adding servers to a unicast cluster triggers an automatic restart of all existing
> servers in the cluster. Plan cluster modifications during maintenance windows to minimize service
> disruption.

To add servers to a cluster:

1.  From Anypoint Platform, select **Runtime Manager**.

2.  Select **Servers**.

3.  Click **Cluster** in the **Type** column to display the details pane:

    ![Add Server button](/mulesoft/current/en-us/hybrid-standalone/_images/rtm-cluster-add-server-to-cluster.png)

    Figure 1. The arrow shows the **Add Server** button in the details pane.

4.  Click **Add Server**.

    Servers that are already in a server group or cluster don’t appear in the list of available
    servers.

5.  In the list, select the servers to add to the cluster, and click **Add Servers**.

    - The servers no longer appear in the **Servers** list.

    - To see the list of servers in the cluster, click the cluster name.

You can remove a server from a cluster without changing the server or cluster.

## Remove Servers from a Cluster

Remove servers from a cluster to reduce processing capacity, perform maintenance, or reallocate
servers to other deployment configurations.

> [!IMPORTANT] When you remove a server from a unicast cluster, all existing servers in the cluster
> restart.

To remove a server from a cluster:

1.  From Anypoint Platform, select **Runtime Manager**.

2.  Select **Servers**.

3.  Click **Cluster** in the **Type** column to display the details pane.

4.  Click the **X** icon to remove the server from the cluster:

    ![X icon](/mulesoft/current/en-us/hybrid-standalone/_images/rtm-remove-server-from-cluster.png)

    Figure 2. The arrow shows the **X** icon in the details pane.

5.  In the **Remove** confirmation window, select the checkbox to verify that you want to remove the
    server from the cluster, and then click the **Remove** button.

## Delete Clusters

When deleting a cluster, consider this:

- Alert definitions and history for the cluster are deleted.

- Servers assigned to the cluster are not deleted.

- Servers assigned to the cluster restart.

- Applications deployed to the servers in the cluster are removed.

To delete a cluster:

1.  From Anypoint Platform, select **Runtime Manager**.

2.  Select **Servers**.

3.  Click **Cluster** in the **Type** column to display the details pane.

4.  Click the cluster status and select **Delete** from the menu:

    ![Delete option](/mulesoft/current/en-us/hybrid-standalone/_images/rtm-cluster-delete.png)

    Figure 3. The arrow shows the **Delete** option in the details pane.

5.  In the confirmation window, select the checkbox to verify that you want to delete the cluster,
    then click **Delete Cluster**.

The servers in the deleted cluster restart.

## See Also

- [Creating Clusters](https://docs.mulesoft.com/hybrid-standalone/creating-clusters)

- [Managing Servers](https://docs.mulesoft.com/hybrid-standalone/managing-servers)

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

- [Deploying Mule Apps to Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/deploying-apps-hybrid-standalone)

<!-- document id=a94ec7a7677c8ef678b94063cf6c41307e150e8377fb5294fdbc089a9a374a4f url=/mulesoft/current/en-us/hybrid-standalone/managing-hybrid-standalone.md -->

---
product: Hybrid Standalone Runtimes
---

# Managing Hybrid Standalone Instances

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

Manage your hybrid standalone runtime instances to maintain optimal performance, ensure high
availability, and scale your infrastructure as your business requirements evolve.

## Manage Servers, Server Groups, and Clusters

Use Runtime Manager to manage your existing servers, server groups, and clusters, enabling ongoing
administration, monitoring, and maintenance of your hybrid standalone infrastructure.

- [Managing Servers](https://docs.mulesoft.com/hybrid-standalone/managing-servers)  
  Individual server administration including health monitoring, configuration updates, and resource
  management

- [Managing Server Groups](https://docs.mulesoft.com/hybrid-standalone/managing-servers-groups)  
  Coordinated management of multiple servers for load distribution and workload balancing

- [Managing Clusters](https://docs.mulesoft.com/hybrid-standalone/managing-clusters)  
  High-availability cluster administration with member coordination and shared resource management

- [High Availability and Disaster Recovery](https://docs.mulesoft.com/hybrid-standalone/hybrid-standalone-hadr)  
  Design hybrid standalone deployments to stay available during component failures and to recover
  from disasters while minimizing downtime and data loss

## Management Operations

- Update server configurations, properties, and environment variables as needed

- Add or remove members from server groups and clusters to scale your infrastructure

- Apply security updates, patches, and maintenance across your managed instances

## See Also

- [Setting up Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/setting-hybrid-standalone)

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

- [Deploying Mule Apps to Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/deploying-apps-hybrid-standalone)

<!-- document id=0d88dfa2d3d57ced92fcd452d903a396628731aced9c2090d61629924b77158f url=/mulesoft/current/en-us/hybrid-standalone/managing-apps-hybrid-standalone.md -->

---
product: Hybrid Standalone Runtimes
---

# Managing Mule Apps Deployed to Hybrid Standalone Instances

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

Manage your deployed Mule applications through Runtime Manager’s centralized console to control
application lifecycle, monitor performance, and maintain operational health across your hybrid
standalone instances.

## Overview

Runtime Manager provides comprehensive application management capabilities for Mule applications
deployed to hybrid standalone instances. You can:

- Monitor application health and performance metrics in real time

- Control application lifecycle operations (start, stop, delete, update)

- Manage individual flow states within deployed applications

- Configure application properties and logging settings

- Access detailed application analytics and transaction insights

- Perform application updates and version management

> [!NOTE] This page covers deployments on hybrid standalone instances that are deployed both through
> the cloud based or the Private Cloud Edition of Anypoint Platform. Some of the features described
> in this page are not yet available on the Anypoint Platform Private Cloud Edition. If you’re
> interested in requesting the Anypoint Platform Private Cloud Edition, contact your sales
> representative.

> [!NOTE] MuleSoft doesn’t support manually deploying apps if you are managing your hybrid
> standalone servers with Runtime Manager. If you manually deploy applications on your hyrbid
> standalone servers, you can’t see or manage them in Runtime Manager because the applications are
> not auto-discovered.

## Applications Dashboard

Access comprehensive application information and management controls through the Applications
dashboard in Runtime Manager.

### Dashboard Access

1.  In Runtime Manager, navigate to the **Applications** tab.

2.  Select any deployed application to open the application details panel.

3.  Review application status, deployment information, and available management actions.

![Applications dashboard showing deployed applications list](/mulesoft/current/en-us/hybrid-standalone/_images/managing-applications-on-your-own-servers-26ef4.png)

### Dashboard Information

The application dashboard displays deployment-specific information based on your target
infrastructure.

**Server Deployments**

- Application status (Running, Stopped, Failed)

- Last modification timestamp

- Deployed application file (JAR/ZIP) with update capability

- Server resource utilization

**Server Group and Cluster Deployments**

- Aggregated application status across all members

- Individual server status within the group or cluster

- Load distribution and member health indicators

- Collective resource consumption metrics

> [!TIP] Click any server name in the deployment panel to access detailed server information and
> diagnostics. For comprehensive server management guidance, refer to
> [Managing Servers](https://docs.mulesoft.com/hybrid-standalone/managing-servers).

### Application Management Actions

The dashboard provides access to key management functions through buttons:

**Manage Application**

- Access comprehensive application settings and configuration options

- Review detailed deployment information and runtime parameters

- Configure application properties, logging, and monitoring settings

- Access performance dashboards and metrics analysis

![Manage Application button on application details panel](/mulesoft/current/en-us/hybrid-standalone/_images/managing-applications-on-your-own-servers-b0e6f.png)

**Insight**

- Analyze transaction-level data for business and technical insights

- Track message flow patterns and performance characteristics

- Investigate errors and performance bottlenecks

- Monitor business process execution and outcomes

![Insight button for application analytics](/mulesoft/current/en-us/hybrid-standalone/_images/managing-applications-on-your-own-servers-ba927.png)

> [!NOTE] Insight features may have limited availability in Anypoint Platform Private Cloud Edition
> environments.

## Application Settings Management

Access comprehensive application configuration and monitoring options.

### Accessing Application Settings

1.  Navigate to Runtime Manager and select the **Applications** tab.

2.  Choose your deployed hybrid standalone application to open the details panel.

3.  Click **Manage Application** to access the full settings interface.

![Application settings interface with configuration tabs](/mulesoft/current/en-us/hybrid-standalone/_images/managing-applications-on-your-own-servers-1fd39.png)

### Settings Interface

The application settings interface provides access to all dashboard information plus additional
management capabilities.

**Configuration Tabs**

- **Flow Monitoring**: Individual flow performance and management controls

- **Insight**: Transaction analytics and business process monitoring

- **Alerts History**: Historical record of triggered application alerts

- **Properties**: Application runtime properties and environment variables

- **Logging**: Log level configuration and output management

The **Alerts History** tab provides comprehensive visibility into application monitoring even\*ts,
including:

- Alert trigger timestamps and conditions

- Alert severity levels and notification status

- Resolution tracking and acknowledgment records

- Performance threshold violations and recovery events

For comprehensive alerting configuration, see
[Creating Alerts for Mule Apps Deployed to Hybrid Standalone](https://docs.mulesoft.com/hybrid-standalone/creating-alerts-hybrid-apps).

## Flow Management

Control individual flow states within your deployed applications to enable granular application
behavior management and troubleshooting capabilities.

### Flow Management Overview

Runtime Manager provides flow-level control for applications deployed to hybrid standalone
instances, enabling you to:

- Start and stop individual flows within running applications

- Override application-defined flow management logic

- Troubleshoot specific integration flows without affecting entire applications

- Implement maintenance workflows for specific business processes

### Before you Begin

- Applications must be deployed to hybrid standalone instances (not available for CloudHub or
  Runtime Fabric)

- User account must have **Manage Applications** permission for target applications

- Target applications must be in Running status

### Flow State Management

**Default Flow Behavior**

All flows within deployed applications start in **Unmanaged** state by default, allowing application
logic to control flow activation and deactivation based on business requirements or runtime
conditions.

**Start and Stop Flows**

Starting a flow activates its processing capability but does not trigger endpoints or initiate
message processing. The flow becomes available to process messages when triggered by configured
sources.

1.  Navigate to your application settings in Runtime Manager.

2.  Access the **Flow Monitoring** tab.

3.  Select one or more flows to manage.

4.  Use **Start** or **Stop** buttons to control flow states.

![Flow Monitoring tab with Start and Stop flow controls](/mulesoft/current/en-us/hybrid-standalone/_images/flow-management-983fd.png)

### Managed vs Unmanaged Flow States

**Unmanaged State (Default)**

Flows operate under application control, allowing custom logic within the Mule application to start
and stop flows based on:

- Business conditions and requirements

- External system availability

- Scheduled operations and maintenance windows

- Error recovery and failover scenarios

**Managed State (Runtime Manager Control)**

When you manually start or stop a flow, Runtime Manager overrides application logic and enforces the
specified state:

- **Active**: Flow remains active regardless of application logic attempts to stop it

- **Inactive**: Flow remains stopped regardless of application logic attempts to start it

**Returning to Unmanaged State**

Click **Unmanage** to restore application-controlled behavior and remove Runtime Manager state
enforcement from a flow.

![Unmanage button to restore application-controlled flow behavior](/mulesoft/current/en-us/hybrid-standalone/_images/flow-management-unmanage.png)

## Start, Stop, and Restart Applications

Control application lifecycle operations through Runtime Manager’s centralized interface for hybrid
standalone deployments.

**Operation Requirements**

- **Servers**: Target server must be accessible and running

- **Server Groups**: At least one server in the group must be running

- **Clusters**: At least one cluster member must be active and accessible

**Start, Stop, and Restart Process**

1.  Navigate to the **Applications** tab in Runtime Manager.

2.  Select your deployed application to open the management panel.

3.  Click the status dropdown arrow next to the application name.

4.  Choose the desired action from the available options:

**Available Actions**

- **Start**: Activates stopped applications

- **Restart**: Resets applications that are already running

- **Stop**: Stops running applications

![AMC\_StopStartDeleteApp](/mulesoft/current/en-us/hybrid-standalone/_images/amc-restartapp.png)

**Operation Behavior**

**Start Applications**

- Activates stopped applications on target servers

- Applies to individual servers, server groups, and clusters

- Ensures proper application initialization and endpoint activation

**Stop Applications**

- Gracefully stops running applications

- Preserves application state and in-flight message processing

- Maintains application configuration for future restarts

**Restart Applications**

- Performs complete application restart cycle

- Redeploys application artifacts if needed

- Refreshes application configuration and connections

**Cluster and Server Group Operations**

For applications deployed to server groups or clusters:

- Operations apply simultaneously to all target servers

- Status indicators show aggregated results across all members

- Individual server status is visible in the deployment details panel

> [!IMPORTANT] Application operations are immediate and affect all target servers. Ensure proper
> coordination for production environments.

## Update Applications

Deploy new versions of your applications to hybrid standalone instances through Runtime Manager’s
update interface.

### Application Update Process

1.  Navigate to the **Applications** tab in Runtime Manager.

2.  Select your deployed application to open the management panel.

3.  Click **Choose file** to select a new application version.

4.  Choose your update source:

**Update Sources**

- **Import file from Exchange**: Deploy from Anypoint Exchange

- **Upload file**: Deploy from local development builds

  1.  Click **Apply changes** to initiate the update process.

### Update Behavior

**Update Process**

- Application status indicator changes to blue during update

- Status returns to green when deployment completes successfully

- Update process typically completes within a few seconds

**Cluster and Server Group Updates**

- New application versions deploy simultaneously to all target servers

- Ensures consistent application state across all infrastructure members

- Maintains deployment synchronization across server groups and clusters

### Grace Period

When stopping, restarting, or updating applications, Runtime Manager implements a grace period to
ensure proper message processing:

- **Two-minute timeout** for in-flight message delivery

- **Five-second runtime grace period** for application shutdown

- Graceful handling of ongoing transactions and business processes

## Delete Applications

Remove deployed applications from your hybrid standalone infrastructure through Runtime Manager’s
application management interface.

**Deletion Requirements**

- **Servers**: Target server must be in Running status

- **Server Groups**: At least one server in the group must be running

- **Clusters**: At least one cluster member must be active and accessible

**Delete Application Process**

Application deletion is immediate and can’t be undone. Ensure you have application backups or source
code access before deletion.

1.  Navigate to the **Applications** tab in Runtime Manager.

2.  Locate the application you want to remove.

3.  Click the status dropdown arrow next to the application.

4.  Select **Delete** from the available actions menu.

![Delete option in application status dropdown menu](/mulesoft/current/en-us/hybrid-standalone/_images/managing-applications-on-your-own-servers-96463.png)

## Redeploy Deleted Applications

Runtime Manager implements automatic recovery mechanisms to maintain application deployment
consistency across your hybrid standalone infrastructure.

**Manual File System Modifications**

When application files are manually modified on the server filesystem while Mule runtime is running:

- Affected applications are automatically undeployed from the local server

- Applications on other servers in groups or clusters remain unaffected

- Only Runtime Manager UI or REST API deletions permanently remove applications

**Runtime Restart Synchronization**

During Mule runtime restart, Runtime Manager performs automatic synchronization as follows.

- Detects applications missing from expected deployment targets

- Automatically redeploys missing applications to restore desired state

- Applies configurations to individual servers, server groups, and clusters

- Synchronization occurs only during runtime restart events

**New Server Integration**

When adding servers to existing server groups or clusters:

- Runtime Manager automatically deploys all group/cluster applications to new members

- Deployment occurs regardless of other member availability

- Ensures deployment consistency across all infrastructure components

## Download an Application Archive

Runtime Manager doesn’t support downloading the application archive (ZIP or JAR file) from the
application **Settings** page for an application deployed to hybrid standalone instances.

However, you can download the archive using these programmatic access methods.

- **Runtime Manager REST API**: Use API endpoints to retrieve application artifacts

- **Anypoint CLI**: Download archives through command-line interface tools

For detailed CLI usage, see
[Runtime Manager Application Artifacts](https://docs.mulesoft.com/anypoint-cli/latest/standalone-apps#runtime-mgr-standalone-application-artifact).

## Application Status

Understand the various status indicators for applications deployed to hybrid standalone instances to
monitor application health and deployment progress.

The information in the **Status** column depends on the context:

### Application Status States

<table><colgroup><col> <col> <col></colgroup><thead><tr><th>Icon</th><th>State</th><th>Description</th></tr></thead><tbody><tr><td><div><div><div><img src="https://docs.mulesoft.com/hybrid-standalone/_images/managing-deployed-applications-a665b.png" alt="managing deployed applications a665b"></div></div></div></td><td><div><div><ul><li><p><strong>Stopped</strong></p></li><li><p><strong>Not Running</strong></p></li><li><p><strong>Undeployed</strong></p></li></ul></div></div></td><td><div><div><p>The application is not running.</p></div></div></td></tr><tr><td><div><div><div><img src="https://docs.mulesoft.com/hybrid-standalone/_images/managing-deployed-applications-515a4.png" alt="managing deployed applications 515a4"></div></div></div></td><td><div><div><ul><li><p><strong>Starting</strong></p></li><li><p><strong>Stopping</strong></p></li><li><p><strong>Undeploying</strong></p></li></ul></div></div></td><td><div><div><p>Application is in the process of transitioning to another state.</p></div></div></td></tr><tr><td><div><div><p><span><img src="https://docs.mulesoft.com/hybrid-standalone/_images/console-overview-green-circle.png" alt="console_overview_green_circle"></span></p></div></div></td><td><div><div><ul><li><p><strong>Started</strong></p></li><li><p><strong>Running</strong></p></li><li><p><strong>Updated</strong></p></li></ul></div></div></td><td><div><div><p>Application is running or the update succeeded.</p></div><div><p>The Application shows Started when running on at least one of the Cluster nodes.</p></div></div></td></tr><tr><td><div><div><p><span><img src="https://docs.mulesoft.com/hybrid-standalone/_images/console-overview-red-circle.png" alt="console_overview_red_circle"></span></p></div></div></td><td><div><div><ul><li><p><strong>Deployment Failed</strong></p></li></ul></div></div></td><td><div><div><p>Application deployment failed.</p></div><div><p>The cause of the failure appears in the console.</p></div></div></td></tr><tr><td><div><div><div><img src="https://docs.mulesoft.com/hybrid-standalone/_images/managing-deployed-applications-ab70d.png" alt="managing deployed applications ab70d"></div></div></div></td><td><div></div></td><td><div><div><p>Application update failed.</p></div></div></td></tr></tbody></table>

### Application Deployment States

<table><colgroup><col> <col> <col></colgroup><thead><tr><th>Icon</th><th>State</th><th>Description</th></tr></thead><tbody><tr><td><div><div><div><img src="https://docs.mulesoft.com/hybrid-standalone/_images/managing-deployed-applications-a665b.png" alt="managing deployed applications a665b"></div></div></div></td><td><div><div><p><strong>Deleted</strong></p></div></div></td><td><div><div><p>Application is deleted.</p></div></div></td></tr><tr><td><div><div><div><img src="https://docs.mulesoft.com/hybrid-standalone/_images/managing-deployed-applications-515a4.png" alt="managing deployed applications 515a4"></div></div></div></td><td><div><div><p><strong>Applying</strong></p></div></div></td><td><div><div><p>Application is in the process of transitioning to another state.</p></div></div></td></tr><tr><td><div><div><p><span><img src="https://docs.mulesoft.com/hybrid-standalone/_images/console-overview-green-circle.png" alt="console_overview_green_circle"></span></p></div></div></td><td><div><div><p><strong>Applied</strong></p></div></div></td><td><div><div><p>Application is running or the update succeeded.</p></div></div></td></tr><tr><td><div><div><p><span><img src="https://docs.mulesoft.com/hybrid-standalone/_images/console-overview-red-circle.png" alt="console_overview_red_circle"></span></p></div></div></td><td><div><div><p><strong>Failed</strong></p></div></div></td><td><div><div><p>Application deployment failed.</p></div><div><p>The cause of the failure appears in the console.</p></div></div></td></tr><tr><td><div><div><div><img src="https://docs.mulesoft.com/hybrid-standalone/_images/managing-deployed-applications-de1b7.png" alt="managing deployed applications de1b7"></div></div></div></td><td><div><div><p><strong>Unknown</strong></p></div></div></td><td><div><div><p>Application’s status is unknown because the server is not responding to the platform (on-premises deployments only).</p></div></div></td></tr></tbody></table>

## Monitor Applications

Manage application deployment lifecycle through Runtime Manager’s centralized controls for updates,
monitoring, and removal operations.

Runtime Manager provides comprehensive monitoring capabilities for applications deployed to hybrid
standalone instances:

- **Performance Dashboards**: Real-time application metrics and resource utilization

- **Transaction Analytics**: Business process monitoring and message flow analysis

- **Alert Management**: Proactive notification for application and infrastructure events

- **Log Management**: Centralized logging aggregation and analysis

For detailed monitoring configuration and usage, see
[Monitoring Mule Apps Deployed to Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/monitoring-apps-hybrid-standalone).

## See Also

- [Deploying Mule Apps to Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/deploying-apps-hybrid-standalone)

- [Monitoring Mule Apps Deployed to Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/monitoring-apps-hybrid-standalone)

- [Creating Alerts for Mule Apps Deployed to Hybrid Standalone](https://docs.mulesoft.com/hybrid-standalone/creating-alerts-hybrid-apps)

- [Monitoring Dashboards for Mule Apps Deployed to Hybrid Standalone](https://docs.mulesoft.com/hybrid-standalone/monitoring-dashboards-hybrid-apps)

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

- [Managing Servers](https://docs.mulesoft.com/hybrid-standalone/managing-servers)

<!-- document id=0df0c734d4e6ba4b2f21b12c5ec708a31d7b73191ccab72fb9bc7c2c794a1c77 url=/mulesoft/current/en-us/hybrid-standalone/managing-properties-hybrid.md -->

---
product: Hybrid Standalone Runtimes
---

# Managing Properties

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

Manage application properties for your Mule applications deployed to hybrid standalone instances
through centralized configuration management, enabling dynamic property updates,
environment-specific settings, and secure property handling across your infrastructure.

## Overview

Runtime Manager offers comprehensive property management for applications deployed to hybrid
standalone instances. Use Runtime Manager to:

- Define and manage application properties centrally through Runtime Manager

- Override application-bundled properties without redeployment

- Configure environment-specific settings for different deployment stages

- Secure sensitive configuration data through encrypted property storage

- Manage properties across individual servers, server groups, and clusters

### Property Management Approaches

- **Properties Files**: Include property placeholder YAML files in application deployment archives

- **Runtime Manager Properties**: Override and manage properties through the Runtime Manager console

- **System Variables**: Configure properties at deployment time using Java system environment
  variables

- **External Configuration**: Use external property sources for advanced configuration management

### Property Precedence

Properties defined in Runtime Manager take precedence over application-bundled properties, enabling
environment-specific configuration without modifying application code.

## Property Security

Runtime Manager implements comprehensive security measures for property management:

- Transmission Security: All property values are encrypted over HTTPS during transmission between
  Runtime Manager and Mule runtime.

- Storage Security: Properties are encrypted when stored in the Runtime Manager internal database.

- Access Control: Property values are displayed only through the Runtime Manager Settings page with
  appropriate permissions.

- Audit Trail: Property modifications are tracked for compliance and security auditing.

> [!IMPORTANT] Modifying properties after application deployment requires restarting the application
> and any associated server groups or clusters to apply changes.

## Add Application Properties by Using a Properties File

Include property placeholder YAML files in your deployable application archive to provide default
configuration values. For comprehensive property file configuration guidance, see
[Configuring Properties](https://docs.mulesoft.com/mule-runtime/latest/configuring-properties).

Mule runtime engine loads file-based properties during application initialization.

## Manage Properties Through Runtime Manager

Runtime Manager provides a centralized interface to configure and manage application properties.
This capability supports environment-specific configuration without requiring application code
changes.

### Add Application properties in Runtime Manager

To configure properties, open the property management interface for your deployed application:

1.  From Anypoint Platform, select **Runtime Manager**.

2.  Click the **Applications** tab.

3.  Click the **Status** column to display the details pane.

4.  Click **Manage Application**.

5.  On the **Settings** page, click the **Properties** tab.

![\*Properties\* tab, \*Key\* and \*Value\* fields, and \*…​\* menu on the \*Settings\* page](/mulesoft/current/en-us/hybrid-standalone/_images/rtm-manage-props.png)

Figure 1. The screenshot shows (**1**) the **Properties** tab, (**2**) the **Key** and **Value**
fields, and (**3**) the **…​** menu on the application **Settings** page.

### Property Configuration Operations

To create properties:

1.  Enter the property name in the **Key** field.

2.  Enter the property value in the **Value** field.

3.  Click **Save** > **Redeploy Application**.

To modify existing properties:

1.  Locate the property in the properties list.

2.  Click the **…​** menu for property-specific actions.

3.  Select **Edit** to modify the property value.

4.  Click **Save** > **Redeploy Application**.

To delete properties:

1.  Locate the property in the properties list.

2.  Click the **…​** menu for the target property.

3.  Select **Delete** to remove the property.

4.  Click **Save** > **Redeploy Application**.

> [!IMPORTANT] All property changes require application redeployment to take effect. Plan property
> modifications during appropriate maintenance windows to minimize service disruption.

## Advanced Property Configuration Methods

These are some alternative methods for overriding app properties:

- Configure an external location to add property placeholders or secure property placeholder files
  to override properties.

- Set Java system environment variables at deployment time to override properties.

  To do this, deploy the app using this command:

  mule -M-Dsecret.key=toSecretPassword -M-Denv=prod -M-Ddb.password=secretPassword -app myApp.zip

  In this case, the system stores the input values only in memory. Because these values are never
  saved to a file, you must provide them for every command execution.

## See Also

- [Deploying Mule Apps to Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/deploying-apps-hybrid-standalone)

- [Managing Mule Apps Deployed to Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/managing-apps-hybrid-standalone)

- [Managing Schedulers](https://docs.mulesoft.com/hybrid-standalone/managing-schedulers-hybrid)

- [Monitoring Mule Apps Deployed to Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/monitoring-apps-hybrid-standalone)

- [Creating Alerts for Mule Apps Deployed to Hybrid Standalone](https://docs.mulesoft.com/hybrid-standalone/creating-alerts-hybrid-apps)

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

<!-- document id=2effdc13c44f411d30cc22334944aa3f613e323eebcdbd1344b3182a5ca67509 url=/mulesoft/current/en-us/hybrid-standalone/managing-schedulers-hybrid.md -->

---
product: Hybrid Standalone Runtimes
---

# Managing Schedulers

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

Manage Scheduler components within your deployed Mule applications through Runtime Manager’s
centralized controls to dynamically adjust scheduled jobs, automated processes, and time-based
integrations without requiring application redeployment.

## Overview

Runtime Manager provides comprehensive scheduler management capabilities for applications deployed
to hybrid standalone instances, enabling you to:

- Control scheduler lifecycle operations (enable, disable, run immediately)

- Modify scheduling frequencies and execution patterns in real-time

- Configure timezone settings for cron-based schedulers

- Monitor scheduler execution status and performance

- Manage multiple schedulers across application flows simultaneously

**Scheduler Management Scope**

Scheduler management is available for applications deployed to hybrid standalone instances
(individual servers, server groups, and clusters). This feature provides runtime control over
Scheduler components defined in your Mule application flows.

**Scheduler Identification**

Runtime Manager identifies each Scheduler component using the naming convention
`polling://{flow_name}`, where `{flow_name}` represents the name of the flow containing the
Scheduler element.

> [!IMPORTANT] Timezone configuration for cron schedulers is available only for hybrid standalone
> deployments. CloudHub and Government Cloud deployments don’t support custom timezone settings.

## Use Cases

Schedule management is useful in these contexts:

- You want to change the schedulers in your application at runtime without redeploying.

- You want to disable a scheduled job while one of the applications you’re connecting to is
  undergoing maintenance.

- You want runtime visibility into the schedulers in your application.

## Considerations and Limitations

When using the **Schedulers** tab, consider this:

- If a scheduled job isn’t triggered because the application isn’t running, Runtime Manager triggers
  the job as soon as the application restarts.

- The scheduler reads the job configuration every time it runs.

  To apply your changes immediately, run your jobs manually after updating the schedule.

## Scheduler Management Operations

Manage scheduler configurations and runtime behavior through Runtime Manager’s Schedulers interface
for applications deployed to hybrid standalone instances.

### Prerequisites

Before managing schedulers, make sure that your application deployment meets these requirements:

- Your application contains one or more Scheduler components defined in Mule flows

- Your application is successfully deployed to hybrid standalone instances (servers, server groups,
  or clusters)

- Your user account has appropriate application management permissions in Runtime Manager

![Scheduler component in the Anypoint Studio canvas](/mulesoft/current/en-us/hybrid-standalone/_images/hybrid-scheduler-studio.png)

Figure 1. The arrow shows the **Scheduler** component in the Anypoint Studio canvas.

### Access Scheduler Management

Go to the scheduler management interface for your deployed application:

1.  In Runtime Manager, click **Applications** in the navigation pane.

2.  Select your deployed application from the applications list.

3.  Click the **Schedulers** tab to access scheduler management controls.

![Schedulers option and checkbox on the Schedulers page](/mulesoft/current/en-us/hybrid-standalone/_images/hybrid-scheduler-rtm.png)

Figure 2. The screenshot shows (**1**) the **Schedulers** option and (**2**) the checkbox on the
**Schedulers** page.

**Scheduler Display Information**

- **Name**: Shows the flow name containing each Scheduler element

- **Status**: Displays current state (enabled/disabled) for each scheduler

- **Schedule**: Lists schedulers in the order they appear in your application

![Checkbox, Disable button, and schedule in the details pane](/mulesoft/current/en-us/hybrid-standalone/_images/hybrid-scheduler-rtm-detail.png)

Figure 3. The screenshot shows (**1**) the checkbox, (**2**) the **Disable** button, and (**3**) the
schedule in the details pane.

### Scheduler Configuration Operations

**Enable/Disable Schedulers**

Control scheduler execution state through bulk or individual operations:

1.  **Bulk Operations**: Select multiple scheduler checkboxes and click **Enable** or **Disable**

2.  **Individual Control**: Select a single scheduler checkbox to modify its state

3.  **Status Verification**: Confirm scheduler state changes in the status indicators

**Cron Scheduler Configuration**

Modify cron-based scheduler settings for complex scheduling patterns:

1.  Select a single cron scheduler checkbox

2.  Update schedule configuration in the details pane:

    - **Cron Expression**: Define minute, hour, day, month, and day-of-week patterns

    - **Timezone**: Configure timezone for execution (hybrid standalone only)

    - **Start Time**: Set the execution start time.

![Schedule configuration in the details pane](/mulesoft/current/en-us/hybrid-standalone/_images/hybrid-scheduler-cron.png)

Figure 4. The arrow shows the cron schedule configuration in the details pane.

**Fixed-Frequency Scheduler Configuration**

Adjust fixed-frequency scheduler settings for regular interval execution:

1.  Select a single fixed-frequency scheduler checkbox

2.  Update schedule configuration in the details pane:

    - **Frequency**: Set the execution interval (seconds, minutes, hours)

    - **Frequency Units**: Select the time unit for the frequency value.

    - **Start Delay**: Configure initial delay before first execution

![Schedule configuration in the details pane](/mulesoft/current/en-us/hybrid-standalone/_images/hybrid-scheduler-fixed-frequency.png)

Figure 5. The arrow shows the fixed-frequency schedule configuration in the details pane.

**Apply Configuration Changes**

Finalize scheduler configuration modifications:

1.  Review all configuration changes in the details pane.

2.  Click **Update** to save all modified settings.

3.  Verify changes take effect on the next scheduler execution cycle.

> [!IMPORTANT] Configuration changes apply immediately for management operations (enable/disable)
> but take effect on the next execution cycle for scheduling modifications (frequency, cron
> patterns).

> [!NOTE] By default, schedules run at the frequency defined in the application. When you change the
> frequency of a schedule from Runtime Manager, the schedule runs at the frequency configured in
> Runtime Manager even if you update and redeploy the same schedule in the application JAR file.

## See Also

- [Managing Mule Apps Deployed to Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/managing-apps-hybrid-standalone)

- [Deploying Mule Apps to Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/deploying-apps-hybrid-standalone)

- [Monitoring Mule Apps Deployed to Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/monitoring-apps-hybrid-standalone)

- [Creating Alerts for Mule Apps Deployed to Hybrid Standalone](https://docs.mulesoft.com/hybrid-standalone/creating-alerts-hybrid-apps)

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

<!-- document id=442be0af13783c5c2f0a0a754a1eaeb2d47632ad0f335472308455bcbb5c95f5 url=/mulesoft/current/en-us/hybrid-standalone/managing-servers-groups.md -->

---
product: Hybrid Standalone Runtimes
---

# Managing Server Groups

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

Manage server groups in your hybrid standalone environment to coordinate multiple servers as unified
deployment targets. Server group management includes adding and removing servers from groups,
maintaining group membership, and performing administrative operations like group deletion while
preserving individual server integrity.

## Add Servers to a Group

Add individual servers to an existing server group to expand your deployment capacity and enable
load distribution across multiple runtime instances.

Make sure that you follow these requirements:

- The target server group already exists.

- At least one server is configured and available.

- No applications are currently deployed on servers you want to add to the group.

To add servers to a server group:

1.  From Anypoint Platform, select **Runtime Manager**.

2.  Select **Servers**.

3.  Click **Group** in the **Type** column to display the details pane.

4.  Click the **Add Server** button:

    ![Add Server button](/mulesoft/current/en-us/hybrid-standalone/_images/rtm-group-add-server-to-group.png)

    Figure 1. The arrow shows the **Add Server** button in the details pane.

    A list of available servers appears.

5.  Select the servers to add to the group, and click **Add Servers**.

    - The servers no longer appear in the **Servers** list.

    - To see the list of servers in the server group, click the group name.

## Remove Servers from a Server Group

To remove a server from a group:

1.  From Anypoint Platform, select **Runtime Manager**.

2.  Select **Servers**.

3.  Click **Group** in the **Type** column to display the details pane.

4.  Click the **X** icon next to the server to remove the server:

    ![X icon](/mulesoft/current/en-us/hybrid-standalone/_images/rtm-remove-server-from-group.png)

    Figure 2. The arrow shows the **X** icon in the details pane.

5.  In the **Remove** confirmation window, select the checkbox to verify that you want to remove the
    server from the group.

6.  Click **Remove**.

## Delete Server Groups

When you delete a server group, these actions occur:

- Alert definitions and history for the server group are deleted.

- Applications deployed to each server in the server group are cloned on each server.

Deleting a server group doesn’t delete, restart, or shut down the assigned servers. The servers
appear on the Servers page. You can deploy applications to them individually or add them to other
server groups or clusters.

To delete a server group:

1.  From Anypoint Platform, select **Runtime Manager**.

2.  Select **Servers**

3.  Click **Group** in the **Type** column to display the details pane.

4.  Click the group status and select **Delete** from the menu:

    ![Delete option](/mulesoft/current/en-us/hybrid-standalone/_images/rtm-group-delete.png)

    Figure 3. The arrow shows the **Delete** option in the details pane.

5.  In the **Delete** confirmation window, select the checkbox to verify that you want to delete the
    server group.

6.  Click **Delete Server Group**.

## Upgrade the Mule Runtime Version in a Runtime Manager Server Group

Follow these steps to upgrade the Mule version in a Runtime Manager server group:

1.  Go to Anypoint Runtime Manager.

2.  Switch to the corresponding environment.

3.  Select **Servers** in the navigation menu.

4.  Select the server group to update.

    1.  In the server group dashboard, select the **Servers** tab and select the server to upgrade.

    2.  In the actions dropdown menu, select **Shutdown**.

    3.  Repeat the previous two steps for each server in your server group.

5.  Open a terminal in the local machine that hosts your Mule instance.

6.  If your Runtime Manager agent version is earlier than 2.2.0, upgrade to the latest version.  
    Go to the current Mule Home directory and run the following commands:

    `cd ${MULE-4.1.5_HOME}/bin`  
    `cp ~/Downloads/agent-setup-2.4.20.zip .`  
    `unzip agent-setup-2.4.20.zip`  
    `./amc_setup -U`

7.  Go to the target directory for the new Mule runtime version and install it:  
    `cd ${MULE-4.3.0_DIRECTORY}`  
    `cp ~/Downloads/mule-ee-distribution-standalone-4.3.0.zip .`  
    `unzip mule-ee-distribution-standalone-4.3.0.zip`

8.  Install the latest agent version:

    `cd mule-enterprise-standalone-4.3.0/bin`  
    `cp ~/Downloads/agent-setup-2.4.20.zip .`  
    `unzip agent-setup-2.4.20.zip`  
    `./amc_setup -I`  
    `rm ../conf/mule-agent.yml`

9.  Copy the following files from the previous Mule runtime /conf directory to the new Mule runtime
    /conf directory:

    - All YAML files (`*.yml`)

    - All keystore files (`*.jks`)

10. Confirm that the DNS configured in mule-agent.yml has the following values:

    websocket.transport: consoleUri: wss://runtime-manager.anypoint.mulesoft.com:443/mule

    authenticationProxy: endpoint: https://data-authenticator.anypoint.mulesoft.com

11. If you installed domains in your previous Mule instance, copy those domains to your new Mule
    instance:

    `cp -R ${MULE-4.1.5_HOME}/domains${MULE-4.3.0_HOME}/domains`

12. Start Mule:  
    `cd ${MULE-4.3.0_HOME}/bin`  
    `./mule start`

13. Go to Runtime Manager to confirm that your Mule applications are deployed and displayed as
    Running.

## See Also

- [Creating Server Groups](https://docs.mulesoft.com/hybrid-standalone/creating-servers-groups)

- [Managing Servers](https://docs.mulesoft.com/hybrid-standalone/managing-servers)

- [Deploying Mule Apps to Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/deploying-apps-hybrid-standalone)

<!-- document id=5c8b6f72b7294e883a98b3245c2a888d0531dc62365c05389476da75eb3f3761 url=/mulesoft/current/en-us/hybrid-standalone/managing-servers.md -->

---
product: Hybrid Standalone Runtimes
---

# Managing Servers

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

Manage individual servers in your hybrid standalone environment through Runtime Manager’s
centralized administration interface. Server management includes accessing configuration settings,
controlling server lifecycle operations, managing custom and discovered properties, and maintaining
security certificates to ensure optimal performance and secure communication.

## Access Server Settings

The server **Settings** page provides centralized access to all configuration and management options
for your hybrid standalone servers. From this page, you can configure custom properties, monitor
server health, manage certificates, and perform essential server operations like restart, shutdown,
or deletion.

To access the **Settings** page:

1.  From Anypoint Platform, select **Runtime Manager**.

2.  Click **Servers**.

3.  Either:

    - Click the **Type** column to display the details pane and click **Manage Server**, **Manage
      Group**, or **Manage Cluster**:

      ![Manage Server button](/mulesoft/current/en-us/hybrid-standalone/_images/rtm-view-server-settings.png)

      Figure 1. The arrow shows the **Manage Server** button in the details pane.

    - Click the name of the server, server group, or cluster on the **Servers** page and then click
      **Settings**:

      ![Settings page](/mulesoft/current/en-us/hybrid-standalone/_images/rtm-server-settings-page.png)

      Figure 2. The arrow shows the option to navigate to the **Settings** page.

## View Server Information

Runtime Manager provides multiple views to monitor and manage your hybrid standalone servers. Access
server information through the servers list, details pane, or comprehensive dashboard views.

### Access the Servers List

View all servers, server groups, clusters, and API gateways in your environment:

1.  From Anypoint Platform, select **Runtime Manager**.

2.  Click the **Servers** tab.

The servers list displays key information for each component:

**Name**

The name of the server, API gateway, server group, or cluster.

**Status**

Current operational status (Running, Disconnected, Created, etc.).

**Type**

Component type: Mule server, API gateway, server group, or cluster.

**Version**

Mule runtime engine or API gateway version number.

### View the Details Pane

Access detailed information and quick actions for a specific server:

1.  From the **Servers** list, click the **Type** column for the server you want to view.

2.  The details pane displays on the right side of the screen.

The details pane provides:

**Overview Information**

- Current status indicator

- Mule runtime engine or API gateway version

- Runtime Manager agent version

- For clusters: cluster type (unicast or multicast)

**Quick Actions**

- **Manage Server**, **Manage Group**, or **Manage Cluster** button to access the Settings page

- **View Dashboard** button to open the server dashboard

  To view the dashboard for a server in a server group or cluster, click the server name in the
  details pane.

**Tabbed Details**

Access additional information through the tabs at the bottom of the details pane:

- **Servers** tab (for groups and clusters): Lists all member servers and their current statuses.

- **Applications** tab: Shows all deployed applications and their operational status.

- **Plugins** tab: Displays configured integrations such as Splunk and ELK.

![Applications tab, servers list, and Plugins tab](/mulesoft/current/en-us/hybrid-standalone/_images/rtm-cluster-details-pane.png)

Figure 3. The screen shows the **Applications** tab, servers list, and **Plugins** tab.

### View the Server Dashboard

Access comprehensive performance metrics and application information through the server dashboard:

1.  From the **Servers** list, click the server name.

2.  The dashboard displays detailed real-time metrics.

**Performance Metrics**

The dashboard provides visual graphs for:

- **Heap Memory**: JVM memory usage over time

- **CPU**: Processor utilization and performance trends

![Heap Memory graph, applications list, and CPU graph](/mulesoft/current/en-us/hybrid-standalone/_images/rtm-server-dashboards-page.png)

Figure 4. The screen shows the **Heap Memory** graph, applications list, and **CPU** graph.

**Application Information**

The dashboard displays for each deployed application:

- Application name and deployment status

- Mule messages processed

- Error messages and exceptions

- Resource utilization details

## Shut Down, Restart, or Delete Servers

In Runtime Manager, you can shut down, restart, or delete a server.

After shutting down a server, you can’t start it from Runtime Manager. You must manually start the
server on the system where Mule runtime engine is installed.

If an error occurs in Runtime Manager during server shutdown or restart, manually start or stop the
server on the system where Mule is installed.

To shut down, restart, or delete a server:

1.  From Anypoint Platform, select **Runtime Manager**.

2.  Select **Servers**.

3.  Click the server name.

4.  Click **Settings**:

    ![\*Actions\* menu](/mulesoft/current/en-us/hybrid-standalone/_images/rtm-servers-actions-menu.png)

    Figure 5. The arrow shows the **Actions** menu on the **Settings** page.

5.  From the **Actions** menu, select:

    - **Delete**

    - **Restart**

    - **Shutdown**

    - **Renew Certificate**

6.  In the confirmation window, select the checkbox to confirm your choice.

## Configure Server Properties

Runtime Manager enables you to view, create, and manage server properties for your hybrid standalone
instances. Server properties are configuration values that control JVM behavior and application
settings across your Mule runtime environments.

### Property Types

- Custom Properties

  - Custom properties are user-defined key-value pairs that configure JVM container settings for
    Mule instances. For example, you can set `ENV=qa` to specify the server environment or
    `MAX_HEAP=2g` for memory allocation.

  - Custom properties are stored in the `$MULE_HOME/conf/wrapper.conf` file on the system where Mule
    is installed.

- Application Properties

  - Application properties defined in Runtime Manager override application properties in
    `mule-app.properties`

  - Application properties defined in the `mule-app.properties` file override server properties
    specified in Runtime Manager

- Discovered Properties  
  Discovered properties are automatically detected configuration values from the remote Mule
  environment, including:

  - JVM arguments

  - Environment properties

  - System properties

Runtime Manager retrieves these values through the Runtime Manager agent, which queries the `System`
Java class on the remote server. By default, auto-discovery is disabled for security reasons. When
enabled, Runtime Manager stores an encrypted version of these properties in its internal database.

To fully disable this feature, contact your MuleSoft customer success representative.

### View and Manage Properties

To view server properties:

1.  From Anypoint Platform, select **Runtime Manager**.

2.  Click **Servers**.

3.  Click the **Type** column to display the details pane.

4.  Click **Manage Server**, **Manage Group**, or **Manage Cluster**.

5.  On the **Settings** page, click **Properties**:

    ![Properties tab](/mulesoft/current/en-us/hybrid-standalone/_images/rtm-server-properties-tab.png)

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

From the **Properties** tab, you can:

- Search for existing properties

- View custom and discovered properties

- Create new custom properties

- Edit existing properties

### View Discovered Properties

To view discovered properties, select **Discovered Properties** and then click **Enable
Auto-Discovery**:

![Discovered Properties and Enable Auto-Discovery buttons](/mulesoft/current/en-us/hybrid-standalone/_images/rtm-server-enable-autodiscovery.png)

Figure 7. The screen shows the **Discovered Properties** and **Enable Auto-Discovery** buttons on
the **Properties** tab.

The server must be running to auto-discover server properties.

### Create Custom Properties

To create new custom properties:

1.  From Anypoint Platform, select **Runtime Manager**.

2.  Click **Servers**.

3.  Click the **Type** column to display the details pane.

4.  Click **Manage Server**, **Manage Group**, or **Manage Cluster**.

5.  On the **Settings** page, click **Properties**.

6.  Click **Custom Properties**.

7.  Enter the property name in the **Key** field.

8.  Enter the property value in the **Value** field.

9.  Click **Save**.

After creating a custom property, restart the server to apply the new property to the Mule
configuration.

## Renew Server Certificates

Registering a Mule server in Anypoint Runtime Manager requires a valid certificate provisioned and
signed by Runtime Manager. The certificate ensures secure communication between Runtime Manager and
the Runtime Manager agent.

When a server certificate expires, Runtime Manager displays `Disconnected` in the **Status** column
for the server on the **Servers** page. The `mule_agent.log` file displays a message like this:

com.mulesoft.agent.transport.WSConnection: Failed attempt to connect nro. 1 to the web socket client
at runtime-manager.anypoint.mulesoft.com: Connection refused.

For applications deployed to the server, Runtime Manager displays `Unknown` in the **Status** column
on the **Applications** page.

### View a Certificate Expiration Date

To view the expiration date for a server:

1.  From Anypoint Platform, select **Runtime Manager**.

2.  Click **Servers**.

3.  Click the server name.

    For servers in a server group or cluster, click the server group or cluster name and then click
    the server name.

    The certificate expiration date appears on the server dashboard:

    ![Certificate expiration date on the Dashboard page](/mulesoft/current/en-us/hybrid-standalone/_images/rtm-server-certificate.png)

    Figure 8. The arrow shows the **Certificate expiration date** on the **Dashboard** page.

### Renew a Certificate from Runtime Manager

Before a certificate expires, you can renew it directly from Runtime Manager.

You can renew a certificate for a specific server or multiple servers within a cluster or group.

The status for the server must be `Running` to update its certificate.

To renew a certificate for a standalone server:

1.  From Anypoint Platform, select **Runtime Manager**.

2.  Click **Servers**.

3.  Verify that the server status is `Running`.

4.  Click the server name.

    ![Select Server](/mulesoft/current/en-us/hybrid-standalone/_images/rtm-server-standalone-name.png)

5.  Click **Settings**.

6.  From the **Actions** menu, select **Renew Certificate**.

    ![Settings Tab](/mulesoft/current/en-us/hybrid-standalone/_images/rtm-server-standalone-settings.png)

7.  Select the checkbox to confirm your choice, and then click **Renew**.

    ![Confirm Renewal](/mulesoft/current/en-us/hybrid-standalone/_images/rtm-server-standalone-renew.png)

8.  Check **Certificate expiration date** to verify that the certificate is renewed successfully,
    and restart Mule runtime to start using the new certificates.

To renew a certificate for servers in a cluster or group:

1.  From Anypoint Platform, select **Runtime Manager**.

2.  Click **Servers**.

3.  Verify that the server status is `Running`.

4.  Click the group or cluster name.

    ![Select Group or Cluster](/mulesoft/current/en-us/hybrid-standalone/_images/rtm-server-certificate-group-name.png)

5.  Check the radio button to select the server or servers you want to update.

6.  From the **Actions** menu, select **Renew Certificate**.

    ![Select Server](/mulesoft/current/en-us/hybrid-standalone/_images/rtm-server-certificate-group-select-server.png)

7.  Select the checkbox to confirm your choice, and then click **Renew**.

    ![Confirm Renewal](/mulesoft/current/en-us/hybrid-standalone/_images/rtm-server-certificate-group-renew.png)

8.  Check **Certificate expiration date** to verify that the certificate renewed successfully.

If the **Renew Certificate** option in the **Actions** pull-down menu isn’t available after
performing the previous steps,
[update your **Agent** version](https://docs.mulesoft.com/runtime-manager/installing-and-configuring-runtime-manager-agent#update-the-agent.adoc).
The **Server certificate renewal** feature, which enables you to renew server certificates directly
from Runtime Manager, was introduced by Runtime Manager 2.8.4. This feature requires Runtime Manager
Agent 1.10.0 or later. Hover over the **Renew Certificate** option in the **Actions** pull-down
menu, and a tooltip in the UI indicates you the minimum required Runtime Agent version.

> [!NOTE] Renewing server certificates requires a manual runtime restart to start using the new
> certificates.

If renewing the unexpired certificate via Runtime Manager fails, follow the steps in
[Renew a Certificate via the Command Line](#renew-a-certificate-via-the-command-line).

### Renew a Certificate via the Command Line

Use this method to renew a certificate even after it has expired.

The agent connects with Runtime Manager using mutual SSL authentication and stores the key pair in
the `$MULE_HOME/conf/mule-agent.jks` file. The key pair is valid for two years, after which the
certificate expires and the connection with Runtime Manager terminates.

> [!NOTE] Make sure you disable MFA before implementing these steps.

To renew the agent key pair:

1.  Download the appropriate `agent-certificate-renewer-{version}.jar` file for your Mule version
    from
    [Applications and Servers showing as Unknown and Disconnected state in Anypoint Runtime Manager due to expired key pair](https://help.salesforce.com/s/articleView?id=001118268&type=1).

2.  Move the JAR file to `$MULE_HOME/bin` and make sure that you have execute permission.

    For example, on Linux, enter `chmod +xx agent-certificate-renewer-{version}.jar`.

3.  Stop Mule.

4.  Create a backup copy of the `$MULE_HOME/conf` directory.

5.  From `$MULE_HOME/bin`, run one of these commands, depending on how you authenticate with
    Anypoint Platform:

    - Nonfederated

      Use your Anypoint Platform credentials on the command line:

      `java -jar ./agent-certificate-renewer-{version}.jar -u <username> -p <password>`

    - External identity

      Copy the registration token for the server from the **Runtime Manager > Servers > Add Server**
      popup screen and include it on the command line:

      ![Add Registration Token](/mulesoft/current/en-us/hybrid-standalone/_images/rtm-server-certificate-external-identity.png)

      And execute this command:

      `java -jar ./agent-certificate-renewer-{version}.jar -H <ServerToken>`

    - Proxy connection

      Use your Anypoint Platform and proxy server credentials on the command line:

      `java -jar agent-certificate-renewer-{version}.jar -u <username> -p <password> -P <host> <port> <username> <password>`

    - US MuleSoft Government Cloud Control Plane

      Use this -r flag:

      `java -jar ./agent-certificate-renewer-{version}.jar -H <ServerToken> -r us_gov`

    - EU Control Plane

      Use this -r flag:

      `java -jar ./agent-certificate-renewer-{version}.jar -u <username> -p <password> -r eu1`

    The command displays these messages:

    INFO: Connecting to Core Services to extract authentication token. INFO: Connecting to Runtime
    Manager to request a new certificate. INFO: Backing up current agent keystore. INFO: Generating
    and saving new keystore.

## See Also

- [Creating Servers](https://docs.mulesoft.com/hybrid-standalone/creating-servers)

- [Managing Server Groups](https://docs.mulesoft.com/hybrid-standalone/managing-servers-groups)

- [Managing Clusters](https://docs.mulesoft.com/hybrid-standalone/managing-clusters)

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

<!-- document id=536f3a0175ddd60c8db536bf4179d234c418eedf0b0fbafe935dadc9a6820570 url=/mulesoft/current/en-us/hybrid-standalone/monitoring-dashboards-hybrid-apps.md -->

---
product: Hybrid Standalone Runtimes
---

# Monitoring Dashboards for Mule Apps Deployed to Hybrid Standalone

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

Monitor your Mule applications deployed to hybrid standalone instances through comprehensive
performance dashboards that provide real-time visibility into application health, business metrics,
and integration performance across your distributed runtime environment.

## Overview

Runtime Manager provides comprehensive application monitoring dashboards for your Mule applications
deployed to hybrid standalone environments, so you can:

- Monitor real-time application performance metrics and transaction flow

- Analyze business transaction patterns and message processing rates

- Track application-specific KPIs and custom business metrics

- Identify performance bottlenecks and integration failures

- Monitor resource consumption and optimize application efficiency

- Correlate application performance with business outcomes

> [!NOTE] To view application dashboards, you must have the Runtime Manager Read Applications
> permission for the target applications.
>
> Anypoint Platform Private Cloud Edition doesn’t support the Anypoint Monitoring dashboard feature.

Runtime Manager provides comprehensive application monitoring through multiple dashboard interfaces
designed for different use cases and deployment scenarios.

## Application Monitoring Dashboards

Monitor your Mule applications through specialized dashboards that provide insights into integration
performance, business transactions, and operational health.

### Overview

Application monitoring dashboards help you understand critical aspects of your integration
performance:

- Performance Analysis: When did usage peaks occur and how did they impact system performance?

- Response Time Correlation: What effect do traffic spikes have on application response times?

- Resource Utilization: How effectively are your applications using available processing resources?

- Error Analysis: What impact do high traffic volumes have on message failure rates?

- Multi-Application Impact: How do resource-intensive applications affect the performance of other
  applications on shared infrastructure?

### Dashboard Types

Runtime Manager provides two application dashboard interfaces optimized for different monitoring
needs:

- Built-in Anypoint Monitoring Dashboard  
  Advanced metrics and comprehensive monitoring capabilities

- Classic Application Monitoring Dashboard  
  Essential metrics for basic application monitoring

The dashboard interface displayed depends on your application’s version, deployment target, and
monitoring configuration.

> [!NOTE] CPU and memory information isn’t immediately available in dashboards after an application
> restarts. To retain historical statistics, use the `dashboardStats` API or enable Anypoint
> Monitoring for persistent data storage.

### Built-in Anypoint Monitoring Dashboard

The built-in Anypoint Monitoring dashboard provides comprehensive application monitoring with
advanced metrics, custom visualizations, and multiple analytical views for in-depth performance
analysis

The dashboard is available for applications that meet these criteria: \* Deployed to CloudHub,
Runtime Fabric, or configured hybrid environments \* Running on Mule 4.x or later versions \*
Anypoint Monitoring enabled and properly configured

For detailed configuration and usage information, refer to
[Built-in Application Dashboard](https://docs.mulesoft.com/monitoring/anypoint-insights) in the Anypoint Monitoring
documentation.

### Classic Application Monitoring Dashboard

The classic application monitoring dashboard provides essential application metrics focusing on core
integration performance indicators: message processing, resource utilization, and system health.

The dashboard is available for applications in these scenarios: \* Deployed to CloudHub and running
Mule versions earlier than 3.8.7 \* Deployed to hybrid standalone instances with basic monitoring
enabled \* Applications without Anypoint Monitoring configured \* Environments where only essential
monitoring is required

> [!NOTE] The Mule Messages graph displays comprehensive message processing data for the application
> during the selected time frame, including successful processing, errors, and throughput patterns.

### Access Application Dashboards

Access application monitoring dashboards directly from Runtime Manager for real-time performance
analysis and troubleshooting.

To access application monitoring dashboards:

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

2.  Click the name of the application you want to monitor.

The dashboard interface displayed depends on your application’s configuration, deployment target,
and monitoring setup.

### Dashboard Navigation and Features

Navigate application dashboards effectively using comprehensive time range selection and interactive
data exploration features.

#### Time Range Selection

Monitor application performance across different time periods using the time range selector:

**Built-in Anypoint Monitoring Dashboard**

![Time range selector for Anypoint Monitoring dashboard](/mulesoft/current/en-us/hybrid-standalone/_images/monitoring-dashboards-time-ranges.png)

**Classic Application Monitoring Dashboard**

![Time range selector for classic application dashboard](/mulesoft/current/en-us/hybrid-standalone/_images/monitoring-dashboards-cbd92.png)

#### Data Aggregation by Time Range

Application metrics are aggregated differently based on the selected time range to optimize
performance and provide meaningful insights:

<table><colgroup><col> <col> <col> <col></colgroup><thead><tr><th><strong>Time Range</strong></th><th><strong>Mule Messages</strong></th><th><strong>Error Count</strong></th><th><strong>Response Time (milliseconds)</strong></th></tr></thead><tbody><tr><td><p><strong>3 Hours</strong></p></td><td><p>Per minute</p></td><td><p>Per minute</p></td><td><p>Per minute</p></td></tr><tr><td><p><strong>24 Hours</strong></p></td><td><p>Per 8 minutes</p></td><td><p>Per 8 minutes</p></td><td><p>Per 8 minutes</p></td></tr><tr><td><p><strong>7 Days</strong></p></td><td><p>Per hour</p></td><td><p>Per hour</p></td><td><p>Per hour</p></td></tr><tr><td><p><strong>2 Weeks</strong></p></td><td><p>Per 2 hours</p></td><td><p>Per 2 hours</p></td><td><p>Per 2 hours</p></td></tr></tbody></table>

Data Visualization Patterns:

- Multi-Worker Applications  
  When applications run on multiple workers, each worker appears as a separate curve on graphs,
  differentiated by color coding.

- Shared Infrastructure  
  Applications deployed to server groups or clusters display aggregated performance metrics as
  unified trend lines.

- Performance Correlation  
  Dashboard data enables correlation between application performance and underlying infrastructure
  utilization.

## See Also

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

- [Creating Alerts for Mule Apps Deployed to Hybrid Standalone](https://docs.mulesoft.com/hybrid-standalone/creating-alerts-hybrid-apps)

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

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

<!-- document id=63a9ea713773c885d28c9bacddb17725e4a453db2912f19f0469e03e8daee443 url=/mulesoft/current/en-us/hybrid-standalone/monitoring-dashboards-hybrid.md -->

---
product: Hybrid Standalone Runtimes
---

# Monitoring Dashboards for Servers, Server Groups, and Clusters

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

Monitor your hybrid standalone infrastructure through comprehensive performance dashboards that
provide real-time visibility into server health, resource utilization, and system performance across
your distributed runtime environment.

## Overview

Runtime Manager provides comprehensive infrastructure monitoring dashboards for your hybrid
standalone environment, so you can:

- Monitor real-time server performance metrics and resource utilization

- Analyze historical trends for capacity planning and optimization

- Track JVM performance including memory usage, garbage collection, and thread activity

- View aggregated metrics across server groups and clusters

- Identify performance bottlenecks and system health issues

- Make data-driven decisions for infrastructure scaling and maintenance

> [!NOTE] To view infrastructure dashboards, you must have the Runtime Manager Read Servers
> permission for the target servers.
>
> Anypoint Platform Private Cloud Edition doesn’t support the Anypoint Monitoring dashboard feature.

Runtime Manager provides these infrastructure monitoring dashboards:

- [Server Monitoring Dashboard](#server-monitoring-dashboard)  
  Individual server performance metrics including CPU, memory, JVM heap usage, garbage collection,
  and detailed memory breakdown

- [Server Group and Cluster Monitoring Dashboard](#server-group-and-cluster-monitoring-dashboard)  
  Aggregated performance metrics for servers organized in groups or clusters with comparative
  analysis capabilities

## Server Monitoring Dashboard

Monitor individual server performance through comprehensive dashboards that provide real-time
visibility into system resources, JVM metrics, and operational health indicators.

The server monitoring dashboard provides detailed insights into your hybrid standalone server
performance, including:

- System resource utilization (CPU, memory, disk I/O)

- JVM heap and non-heap memory allocation and usage

- Garbage collection performance and frequency

- Thread management and execution metrics

- Memory breakdown by allocation pools (Eden, Survivor, Old Generation)

- Class loading and code cache utilization

### Access Server Dashboard

To access the server monitoring dashboard:

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

2.  Click the name of the server to monitor.

    The server dashboard displays with comprehensive performance metrics:

    ![Monitoring dashboard for a server](/mulesoft/current/en-us/hybrid-standalone/_images/monitoring-dashboards-server.png)

You can also navigate to individual server dashboards from the
[server group or cluster dashboard](#server-group-and-cluster-monitoring-dashboard) by clicking
individual server names.

### Dashboard Navigation and Features

The server monitoring dashboard provides two complementary tab views for comprehensive performance
analysis:

- **Overview**  
  High-level system metrics including CPU usage, heap memory, and overall server health

- **Breakdown**  
  Detailed JVM memory analysis with individual allocation pools and garbage collection metrics

#### Time Range Selection

Monitor performance across different time periods using the time range selector:

![Time range selector for monitoring dashboards](/mulesoft/current/en-us/hybrid-standalone/_images/monitoring-dashboards-cbd92.png)

Available time ranges include:

- **3 Hours**: Real-time monitoring with minute-level granularity

- **24 Hours**: Recent performance with 8-minute averaging

- **7 Days**: Weekly trends with hourly data points

- **2 Weeks**: Historical analysis with 2-hour averaging

#### Interactive Data Exploration

Enhance your analysis with interactive dashboard features:

- Display numerical values and timestamps by hovering over graph points

- When multiple applications run on the server, filter performance data by specific applications
  using the application checkboxes

![Hover tooltip showing detailed metrics information](/mulesoft/current/en-us/hybrid-standalone/_images/monitoring-dashboards-hover.png)

The memory usage graphs on the dashboards track these values:

- **Usage**  
  Current memory consumption (MB) - indicates active memory allocation

- **Total**  
  Maximum available memory (MB) - represents the upper limit for memory allocation

- **Committed**  
  Memory guaranteed by the JVM (MB) - always greater than or equal to used memory

> [!NOTE] If the JVM attempts to increase used memory beyond committed memory, allocation fails even
> when total memory is available. Monitor committed vs. used memory ratios for optimal performance.

### Overview Tab

The Overview tab provides essential system health metrics for rapid assessment of server performance
and resource utilization.

**Heap Memory**

Monitor JVM heap memory allocation and usage patterns to optimize application performance:

![Heap Memory monitoring dashboard with usage metrics](/mulesoft/current/en-us/hybrid-standalone/_images/monitoring-dashboards-heap.png)

- Heap Memory Usage: Current heap allocation in MB

- Total Heap Memory: Maximum heap size configured for the JVM

- Heap Committed Memory: Memory guaranteed by the JVM for heap operations

Use heap memory metrics to:

- Identify memory leaks and excessive allocation patterns

- Optimize JVM heap size configuration (`-Xmx` and `-Xms` parameters)

- Plan capacity for application deployment and scaling

> [!NOTE] If heap usage consistently approaches total memory, consider increasing heap size or
> analyzing application memory usage patterns. See the [Breakdown Tab](#breakdown-tab) for detailed
> memory pool analysis.

**CPU**

Track processor utilization and system load to ensure optimal server performance:

![Monitoring dashboard for CPU](/mulesoft/current/en-us/hybrid-standalone/_images/monitoring-dashboards-cpu.png)

> [!NOTE] CPU metrics are not available on Windows environments due to platform-specific monitoring
> constraints.

- **CPU Usage**  
  Percentage of processing capacity utilized

- **Available Processors**  
  Number of CPU cores available to the JVM

- **Load Average**  
  Average number of processes waiting for CPU execution

Load Average Interpretation:

- Load < CPU Count: System has spare processing capacity

- Load = CPU Count: System is optimally utilized

- Load > CPU Count: System is experiencing processing pressure and potential performance degradation

### Breakdown Tab

The Breakdown tab provides detailed JVM memory analysis with granular metrics for each memory pool,
enabling precise performance tuning and troubleshooting.

#### JVM Memory Architecture

Understanding JVM memory organization is essential for effective performance monitoring:

- Heap Memory Pools

  - [Eden Space](#eden)

  - [Survivor Space](#survivor)

  - [Old Generation](#old_gen)

- Non-Heap Memory Areas

  - [Code Cache](#code_cache)

  - [Compressed Class Space](#compressed_class)

  - [Metaspace](#metaspace)

Eden Space

Monitor the primary object allocation area for young generation garbage collection optimization:

![Monitoring dashboard for Eden Space](/mulesoft/current/en-us/hybrid-standalone/_images/monitoring-dashboards-eden.png)

Eden space metrics help you:

- Optimize object allocation patterns

- Tune young generation garbage collection frequency

- Identify excessive short-term object creation

Survivor Space

Track intermediate object storage for garbage collection lifecycle analysis:

![Monitoring dashboard for Survivor Space](/mulesoft/current/en-us/hybrid-standalone/_images/monitoring-dashboards-survivor.png)

Survivor space monitoring enables:

- Analysis of object promotion patterns to old generation

- Optimization of survivor space sizing for GC efficiency

- Detection of objects with intermediate lifespans

Old Generation

Monitor long-term object storage and major garbage collection patterns:

![Monitoring dashboard for Old Generation](/mulesoft/current/en-us/hybrid-standalone/_images/monitoring-dashboards-tenure.png)

Old generation metrics provide insight into:

- Long-lived object accumulation patterns

- Major garbage collection frequency and impact

- Memory leak detection through trend analysis

Code Cache

Monitor JIT compiler performance and native code storage:

![Monitoring dashboard for Code Cache](/mulesoft/current/en-us/hybrid-standalone/_images/monitoring-dashboards-cache.png)

Code cache metrics help optimize:

- JIT compilation effectiveness

- Native code storage allocation

- Application startup and runtime performance

Compressed Class Space

Track compressed ordinary object pointer (OOP) storage efficiency:

This metric is available only when using JDK 8+.

![Monitoring dashboard for Compressed Class Space](/mulesoft/current/en-us/hybrid-standalone/_images/monitoring-dashboards-class-space.png)

Monitor compressed class space for:

- Memory efficiency of compressed OOPs

- Class metadata storage optimization

- JVM memory footprint reduction

Metaspace

Monitor class metadata storage using native memory allocation:

This metric is available only when using JDK 8+.

![Monitoring dashboard for Metaspace](/mulesoft/current/en-us/hybrid-standalone/_images/monitoring-dashboards-meta.png)

Key Considerations:

- 256 MB metaspace allocation

- Uses system memory outside JVM heap

- Grows automatically based on class loading requirements

  Metaspace monitoring helps:

- Prevent class metadata memory exhaustion

- Optimize class loading and unloading patterns

- Manage application deployment in memory-constrained environments

#### System Performance Metrics

Monitor JVM runtime performance and system behavior through these key performance indicators:

- [Thread Count](#thread_count)

- [Garbage Collection](#garbage_collection)

- [Class Loading](#class_loading)

Thread Count

Track JVM thread usage to identify concurrency issues and optimize thread pool configuration:

![Monitoring dashboard for Thread Count](/mulesoft/current/en-us/hybrid-standalone/_images/monitoring-dashboards-threads.png)

Monitor thread count to:

- Detect thread leaks and excessive thread creation

- Optimize application concurrency settings

- Identify potential deadlock conditions

Garbage Collection

Monitor garbage collection efficiency across different heap generations:

![Monitoring dashboard for Garbage Collection](/mulesoft/current/en-us/hybrid-standalone/_images/monitoring-dashboards-garbage.png)

Garbage Collection Areas:

- Young Generation: Collection frequency for short-lived objects in Eden and Survivor spaces

- Old Generation: Collection patterns for long-lived objects requiring more intensive cleanup

  Use GC metrics to:

- Optimize heap size allocation between generations

- Identify memory allocation patterns causing excessive GC pressure

- Tune garbage collection algorithms for application performance

Class Loading

Track dynamic class loading across all applications in the JVM:

![Monitoring dashboard for Class Loading](/mulesoft/current/en-us/hybrid-standalone/_images/monitoring-dashboards-classloading.png)

Monitor class loading to:

- Identify classloader memory leaks

- Optimize application startup performance

- Analyze dynamic code loading patterns

## Server Group and Cluster Monitoring Dashboard

Monitor distributed infrastructure performance through aggregated dashboards that provide unified
visibility across multiple servers organized in groups or clusters.

### Overview

Server group and cluster monitoring enables centralized performance analysis across your distributed
hybrid standalone infrastructure, providing:

- Combined view of CPU, memory, and heap utilization across all servers

- Side-by-side performance comparison between individual servers

- Load distribution patterns across server infrastructure

- Collective resource utilization for infrastructure planning

The group and cluster dashboard displays essential aggregated infrastructure metrics:

- CPU Usage: Aggregate processing capacity utilization across all servers (percentage)

- Memory Usage: Combined memory consumption across the infrastructure (MB)

- Heap Total: Aggregate JVM heap allocation for all servers (MB)

- Individual Server Breakdown: Per-server performance within the group context

Aggregated metrics appear as unified plot lines representing the collective performance of selected
servers.

### Access Group and Cluster Dashboards

To monitor aggregated performance metrics for your server infrastructure:

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

2.  Click the server group or cluster name to display the aggregated dashboard.

3.  Select specific servers from the list to display comparative metrics in the details pane.

### Dashboard Navigation

- Time Range Selection

Monitor performance trends across different time periods:

![Monitoring dashboard for a server group or cluster](/mulesoft/current/en-us/hybrid-standalone/_images/monitoring-dashboards-cbd92.png)

Choose from available time ranges: \* **3 Hours**: Real-time infrastructure monitoring \* **24
Hours**: Recent performance analysis \* **7 Days**: Weekly infrastructure trends \* **2 Weeks**:
Historical capacity analysis

- Server-Focused View

Access server-specific performance data within the group context:

![Monitoring dashboard for a server group or cluster](/mulesoft/current/en-us/hybrid-standalone/_images/monitoring-dashboards-6fe9f.png)

From the group dashboard, navigate to individual server dashboards by clicking server names to
access detailed performance metrics and troubleshooting information.

### Troubleshooting Server Group Monitoring

If monitoring metrics don’t appear immediately after configuring Anypoint Monitoring for servers in
a server group, follow this systematic installation process:

1.  In Anypoint Platform go to **Runtime Manager** > **Servers** > **Add Server** to create an
    Anypoint Runtime Manager token.

2.  Execute the command provided in the **Add Server** screen.

3.  In Anypoint Platform go to **Runtime Manager** > **Servers** > **Create Group** to create the
    server group.

4.  Start Mule for all the servers to be added to the server group by using the command
    `./mule start` from the `$MULE_HOME/bin` directory.

5.  In Anypoint Platform go to **Runtime Manager** > **Servers**, click the server group name, and
    **Add Server** to add all the servers to the group.

6.  Deploy an API to the server group.

7.  Stop any running filebeat process in all the servers of the server group and run the `./install`
    command from the `$MULE_HOME/am/bin` directory in all the servers of the server group.

8.  In Anypoint Platform go to **Runtime Manager** > **Servers**, click the server group name, and
    restart all the servers in the server group via **Actions** > **Restart**.

9.  Run `./setup` from the `$MULE_HOME/am/bin` for all the servers in the server group.

    If after this step the metrics don’t show up, repeat the last two steps.

## See Also

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

- [Creating Alerts for Servers, Server Groups, and Clusters](https://docs.mulesoft.com/hybrid-standalone/creating-alerts-hybrid)

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

- [Managing Servers](https://docs.mulesoft.com/hybrid-standalone/managing-servers)

- [Managing Server Groups](https://docs.mulesoft.com/hybrid-standalone/managing-servers-groups)

- [Managing Clusters](https://docs.mulesoft.com/hybrid-standalone/managing-clusters)

<!-- document id=4b3647475e6e92686d9c48c861f8383c1019f73b47a8cbaebdb1f1ba90533816 url=/mulesoft/current/en-us/hybrid-standalone/monitoring-hybrid-standalone.md -->

---
product: Hybrid Standalone Runtimes
---

# Monitoring Hybrid Standalone Instances

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

Monitor your hybrid standalone instances to ensure optimal performance, maintain system health, and
enable proactive problem resolution across your distributed Mule runtime environment.

Runtime Manager provides comprehensive monitoring capabilities for your hybrid standalone
infrastructure through integrated dashboards and alerting systems.

## Creating Alerts

Set up alerts to get email notifications when servers go down, use too much memory or CPU, or when
applications fail. This helps you fix problems quickly.

[Creating Alerts for Server, Server Groups or Clusters](https://docs.mulesoft.com/hybrid-standalone/creating-alerts-hybrid)

## Monitoring Dashboards

View charts and graphs to see how much CPU and memory your servers are using, check application
performance, and spot problems before they become serious.

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

> [!IMPORTANT] When running Mule on Windows systems, the Mule service must be started by a user
> account that belongs to the **Performance Log Users** group to enable proper dashboard
> functionality.

## See Also

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

- [Setting up Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/setting-hybrid-standalone)

- [Deploying Mule Apps to Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/deploying-apps-hybrid-standalone)

<!-- document id=524425a2a0a45c0ca50a85017fc0f3d905a9d46014957ff4b4f7a9614c7ca47e url=/mulesoft/current/en-us/hybrid-standalone/monitoring-apps-hybrid-standalone.md -->

---
product: Hybrid Standalone Runtimes
---

# Monitoring Mule Apps Deployed to Hybrid Standalone Instances

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

Monitor your Mule applications deployed to hybrid standalone instances to ensure optimal
performance, maintain integration health, and enable proactive problem resolution across your
distributed application environment.

Runtime Manager provides comprehensive application monitoring capabilities for your hybrid
standalone Mule applications through integrated dashboards and alerting systems.

## Creating Alerts

Set up email notifications for critical application events such as deployment failures, high error
rates, response time degradation, or custom business metrics to enable rapid response to integration
issues.

[Creating Alerts for Mule Apps Deployed to Hybrid Standalone](https://docs.mulesoft.com/hybrid-standalone/creating-alerts-hybrid-apps)

## Monitoring Dashboards

Track key application performance indicators including message throughput, error rates, response
times, and resource consumption to understand application health and identify optimization
opportunities.

[Monitoring Dashboards for Mule Apps Deployed to Hybrid Standalone](https://docs.mulesoft.com/hybrid-standalone/monitoring-dashboards-hybrid-apps)

## See Also

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

- [Deploying Mule Apps to Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/deploying-apps-hybrid-standalone)

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

<!-- document id=aeffde3f65f87070d2a91eafc15c5a349eab8d2fe2dd030d841f8252706c5f4c url=/mulesoft/current/en-us/hybrid-standalone/hybrid-standalone-requirements-limitations.md -->

---
product: Hybrid Standalone Runtimes
---

# Requirements and Limitations for Hybrid Standalone Instances

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

Plan and configure your hybrid standalone infrastructure by understanding the licensing
requirements, infrastructure specifications, and operational limitations that govern hybrid
standalone deployments.

## MuleSoft License Compliance

You are responsible for ensuring compliance with your MuleSoft licensing for hybrid standalone
deployments.

Licensing is based on the maximum allocated cores consumed by your Mule runtime instances:

- Core calculation is based on logical or allocated cores available to the Mule instance or server.

- Allocated cores are configured through OS, VM, container, or Mule configuration settings.

- Core count is determined by the number of cores visible to the Java Virtual Machine running Mule.

- Physical cores are not considered in licensing; only logical or virtual cores as reported by the
  OS are counted.

- Each VM or container instance is metered separately, even if multiple instances run on the same
  physical host.

- Fractional cores are always rounded up to the nearest integer value.

If cores are not explicitly allocated to Mule, the number of logical or virtual cores available on
the physical or virtual machine or container as informed by the OS determines the core count.

## Requirements

Ensure your infrastructure meets the minimum specifications and configuration requirements for
successful hybrid standalone deployment and operation.

### Hardware Requirements

Minimum hardware specifications for Mule runtime engine on hybrid standalone instances:

- 2 GHz CPU or 1 virtual CPU in virtualized environments, 2+ cores recommended for production
  workloads.

- 1 GB RAM minimum (Mule runtime), 4GB RAM minimum recommended for hybrid deployments, 8GB+
  recommended for production environments.

- 4 GB minimum (Mule runtime), 10GB+ available disk space recommended for applications and logs.

- x86 and x64 architectures supported.

- Reliable internet connectivity for Anypoint Platform communication.

> [!NOTE] Adjust RAM allocation to match your latency requirements and the size and number of
> simultaneous messages that applications process.

### Software Requirements

Verify that you use a supported version of Java before installing Mule runtime engine:

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><div><div><p>JDK</p></div></div></td><td><div><div><p>JDK 17</p></div></div></td></tr></tbody></table>

> [!NOTE] Though you can run a different JDK of choice, MuleSoft doesn’t support or take action to
> fix issues if they are traced back to the JDK.

### Supported Operating Systems

Mule is supported on any operating system that runs a Java Runtime Environment (JRE) from a
supported JDK.

Mule runtime engine passed functional testing against these software and operating systems:

- MacOS 10.15

- HP-UX 11i V3

- AIX 7.2

- Windows Server 2019

- Windows 10

- Solaris 11.3

- Red Hat Enterprise Linux 9.4

- Ubuntu Server 20.04

- Adoptium OpenJDK distribution

> [!NOTE] Anypoint Monitoring agent has known compatibility limitations on all of the operating
> systems listed previously. Advanced monitoring features provided by Anypoint Monitoring may not be
> available on these platforms. Basic monitoring capabilities through Runtime Manager remain
> available.

### Network Requirements

Network configuration needs:

- Outbound HTTPS connectivity to Anypoint Platform

- Firewall configuration for Runtime Manager agent

- Optional VPN for secure communication

- Load balancer configuration (for clustered deployments)

### Security Considerations

Important security aspects:

- SSL/TLS encryption for all communications

- Certificate management and rotation

- Access control and authentication

- Network segmentation and firewall rules

- Audit logging and monitoring

## Limitations

Be aware of the constraints and limitations that affect hybrid standalone deployments to plan your
infrastructure accordingly.

A target represents any deployment destination for Mule applications, including individual servers,
server groups, or clusters. For example, a server group with eight servers is a single target for
deployment purposes.

### Infrastructure Scaling Limits

Design your server infrastructure within these hard limits to ensure scalable and manageable hybrid
standalone deployments.

<table><colgroup><col> <col></colgroup><thead><tr><th>Component</th><th>Hard Limit</th></tr></thead><tbody><tr><td><p>Maximum number of servers (not Runtime Fabric)</p></td><td><p>500</p></td></tr><tr><td><p>Maximum number of servers per server group</p></td><td><p>20</p></td></tr><tr><td><p>Maximum number of servers per cluster</p></td><td><p>8</p></td></tr></tbody></table>

### Network Configuration Requirements

Proper network configuration is essential for Runtime Manager agent connectivity and secure
communication with Anypoint Platform services. Network allowlists, firewall rules, and port
configurations must be properly configured to ensure reliable hybrid standalone operations.

For comprehensive network configuration guidance, refer to
[Adding Ports, IPs, and Hostnames for Runtime Manager Agent](https://docs.mulesoft.com/hybrid-standalone/configure-ports-ips).

### Deployment Limits

Plan your application deployment strategy within these tested and recommended limits to make sure
reliable performance and avoid platform constraints.

<table><colgroup><col> <col></colgroup><thead><tr><th>Component</th><th>Tested Recommended Limit</th></tr></thead><tbody><tr><td><p>Maximum number of deployments per environment</p></td><td><p>1000</p></td></tr><tr><td><p>Maximum number of deployments per hybrid target</p></td><td><p>200</p></td></tr><tr><td><p>Maximum number of properties per application</p></td><td><p>300</p></td></tr><tr><td><p>Maximum deployment size for CloudHub and standalone</p></td><td><p>200 MB</p></td></tr><tr><td><p>Maximum deployment size for CloudHub 2.0 and Runtime Fabric</p></td><td><p>350 MB</p></td></tr></tbody></table>

## See Also

- [Hybrid Standalone Runtimes Overview](https://docs.mulesoft.com/hybrid-standalone/)

<!-- document id=65579eba740c1d8c7cf5433f4706aa71964f3f4fb9ed6576c4516e2a3f686833 url=/mulesoft/current/en-us/hybrid-standalone/setting-hybrid-standalone.md -->

---
product: Hybrid Standalone Runtimes
---

# Setting up Hybrid Standalone Instances

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

Set up hybrid standalone instances to enable centralized management and deployment of Mule
applications through Anypoint Platform while maintaining control over your infrastructure.

## Overview

The setup process includes:

- Prepare infrastructure and plan deployment

- Install and configure Mule runtime engine (Mule)

- Install and set up Runtime Manager agent

- Create servers, server groups, and clusters with Anypoint Platform

- Configure and validate initial setup

## Prepare Infrastructure

Before setting up hybrid standalone instances, make sure your infrastructure meets these
requirements:

- Allocate adequate CPU, memory, and storage for your Mule runtime instances

- Configure outbound HTTPS connectivity (port 443) and firewall rules for Runtime Manager agent

- Use supported OS versions (Linux, Windows, macOS) with compatible Java versions

- Obtain Anypoint Platform subscription

## Install and Configure Mule Runtime

Set up your Mule runtime environment:

- Download and install Mule runtime engine  
  Download the appropriate Mule version and set up your environment with proper configuration. For
  detailed installation instructions, see
  [Download, Install, Configure, and Upgrade On-Premises Mule Runtime Engine](https://docs.mulesoft.com/on-premises/latest/runtime-installation-task).

- Configure runtime properties and settings  
  Configure memory settings, environment variables, and connection properties through the
  `wrapper.conf` file. For configuration options, see
  [Configuring Properties](https://docs.mulesoft.com/mule-runtime/latest/configuring-properties) and
  [Mule Configuration File](https://docs.mulesoft.com/mule-runtime/latest/about-mule-configuration). To point Mule at a
  non-US Cloud control plane, see
  [Configuring Mule to Access Anypoint Platform Control Planes](https://docs.mulesoft.com/control-planes/configuring-mule-control-planes).

- Install enterprise license  
  Install your MuleSoft Enterprise license for production deployments. See
  [Install an Enterprise License on On-Premises Mule Runtime Engine](https://docs.mulesoft.com/on-premises/latest/installing-an-enterprise-license)
  for complete instructions.

- Run Mule as a service  
  Configure Mule as a system service for automatic startup and management. See
  [Download, Install, Configure, and Upgrade On-Premises Mule Runtime Engine](https://docs.mulesoft.com/on-premises/latest/runtime-installation-task)
  for service installation instructions.

- Harden your installation  
  Apply security best practices for production environments. See
  [Harden Your On-Premises Mule Runtime Engine Installation](https://docs.mulesoft.com/on-premises/latest/hardening-your-mule-installation)
  for security configuration guidance.

## Install and Set Up Runtime Manager Agent

The Runtime Manager agent is a lightweight component that enables communication between your
on-premises Mule runtime instances and Anypoint Platform in the cloud.

With the Runtime Manager agent, you can:

- Register servers with Anypoint Platform for centralized management

- Deploy and manage applications remotely through Runtime Manager

- Monitor server health, performance metrics, and application status

- Configure server properties and environment variables

- Receive real-time alerts and notifications

- Access application logs and diagnostic information

For detailed configuration and setup instructions, refer to
[Runtime Manager Agent](https://docs.mulesoft.com/runtime-manager/runtime-manager-agent).

## Create Servers, Server Groups, and Clusters

Use Runtime Manager to create your servers with Anypoint Platform, enabling centralized management
and deployment. Once registered, you can organize servers into groups or clusters and deploy
applications to them.

### Servers

[Creating Servers](https://docs.mulesoft.com/hybrid-standalone/creating-servers)  
Individual server instances that provide a single deployment target for Mule applications. Servers
are ideal for:

- Development and testing environments

- Simple deployments with minimal complexity

- Scenarios where you need direct control over individual server instances

- Applications that don’t require high availability or load distribution

Each server runs independently and can be managed separately through Runtime Manager.

### Server Groups

[Creating Server Groups](https://docs.mulesoft.com/hybrid-standalone/creating-servers-groups)  
Multiple servers organized together to act as a single deployment target. Server groups are ideal
for:

- Production environments requiring redundancy without cluster complexity

- Scenarios where you need to deploy applications to multiple servers simultaneously

- Load distribution across multiple servers for increased traffic handling

- Centralized management of properties, monitoring, and alerts

- Applications that can run independently on each server without shared state

Each server in the group runs its own copy of the application, providing redundancy if one server
fails.

### Clusters

[Creating Clusters](https://docs.mulesoft.com/hybrid-standalone/creating-clusters)  
High-availability configuration where multiple servers work together as a unified system. Clusters
are ideal for:

- Mission-critical applications requiring maximum availability and performance

- Scenarios where automatic failover and load balancing are essential

- Applications that need synchronized communication and shared state

- Zero-downtime deployments and rolling updates

- High-traffic environments requiring automatic traffic distribution

Cluster members work together as a unified system with automatic failover and load balancing.

All servers within a server group or cluster must have identical versions of:

- Mule runtime engine

- Runtime Manager agent

### Registration Workflow

1.  Use Runtime Manager to register each server and configure its properties

2.  Add registered servers to a server group or cluster based on your requirements

3.  Select the individual server, server group, or cluster for your application deployments

## Configure and Validate Initial Setup

Verify your hybrid standalone configuration:

- Test network connectivity to Anypoint Platform and verify DNS resolution

- Confirm Runtime Manager agent is running and communicating with Anypoint Platform

- Verify servers appear in Runtime Manager with "Running" status

- Test server management operations and application deployment capabilities

## See Also

- [Creating Servers](https://docs.mulesoft.com/hybrid-standalone/creating-servers)

- [Creating Server Groups](https://docs.mulesoft.com/hybrid-standalone/creating-servers-groups)

- [Creating Clusters](https://docs.mulesoft.com/hybrid-standalone/creating-clusters)

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

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

- [Deploying Mule Apps to Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/deploying-apps-hybrid-standalone)