Contact Us 1-800-596-4880
  1. Homepage
  2. Hybrid Standalone
  3. Monitoring Mule Apps Deployed to Hybrid Standalone Instances

  4. Creating Alerts for Mule Apps Deployed to Hybrid Standalone

Creating Alerts for Mule Apps Deployed to Hybrid Standalone

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 provides comprehensive alerting capabilities for monitoring your Mule applications deployed to hybrid standalone instances, including:

  • Application performance monitoring (response time, throughput, resource usage)

  • Business transaction tracking and error detection

  • Custom application metrics and notifications

  • Deployment lifecycle event monitoring

  • Integration-specific health and availability monitoring

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 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 for more information.

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

  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.

    • Subject

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

      The subject can include variables. See 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.

    • 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

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

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

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

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.

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

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

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.

Number of errors

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

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

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

These alerts for applications deployed to local servers require no additional parameters:

  • Application undeployed

  • Deployment failure

  • Deployment success

Alert Variables

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

You can’t use the character combination $& in variable expressions.
Table 1. Application Alert Variables
Alert Category Alert Type Available Variables

All Alerts

${resource} ${severity} ${state}

CloudHub App Alerts

CPU usage - CloudHub

${operator} ${value}

Memory usage - CloudHub

Custom application notification

${user} ${priority} ${transactionId} ${message}

Deployment failed

${user} ${message}

Deployment success

${user}

Worker not responding

Exceeds event traffic threshold

${period} ${periodTimeUnit}

Hybrid App Alerts

All Hybrid App Alerts

${name}

Number of Mule messages

${currentValue} ${threshold} ${location}

Number of errors

Response time
Table 2. Variable Definitions
Variable Definition

${currentValue}

Current value of metric that triggers the alert

${location}

Where to find more information about the alert

${message}

Message from the notification that trigger the alert

${name}

Name of the app that triggers the alert

${operator}

An operator, such as < > =

${period}

Period of time over which to measure

${periodTimeUnit}

Period of time unit

${priority}

Priority of the notification that triggers the alert

${resource}

Name of the app that triggers the alert

${severity}

Severity of the alert

${state}

State of the resource that triggers the alert, such as Running or Disconnected

${threshold}

Count over the period of time that triggers the alert

${transactionId}

Transaction ID defined in the app or assigned by Mule

${user}

Anypoint Platform organization name

${value}

A value associated with an element

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
    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
    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
    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
    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
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
    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
    Figure 9. The arrow shows the alert switch off.

    The Active column changes from No to Yes.

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
    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
    Figure 11. The arrow shows the Delete alert (trash can) icon.

  3. Click OK.

See Also