| Key | Description |
|---|---|
| A string value that represents the name of the application. |
| A string value that represents the path of the temporary file used to deploy the application. |
| A Map<String, String> that represents the application properties. |
| Parameter | Description |
|---|---|
| Configures the Runtime Manager agent to use an unencrypted connection. The default TCP port is 9999, so you can connect to the Runtime Manager agent at the base URL |
| Parameter | Description |
|---|---|
| Configures the Runtime Manager agent to establish a TLS connection with an on-premises administration console. Provide the keystore (public-private key pair) and truststore files in JKS format. |
| Issue | Description |
|---|---|
SE-8011 | Agent setup returns |
| Component | Tested/Recommended Limit |
|---|---|
Maximum number of deployments per environment | 1000 |
Maximum number of deployments per hybrid target (not Runtime Fabric) | 200 |
Maximum number of properties per application | 300 |
Maximum deployment size for CloudHub and standalone | 200 MB |
Maximum deployment size for CloudHub 2.0 and Runtime Fabric | 350 MB |
| Component | Hard Limit |
|---|---|
Maximum number of servers (not Runtime Fabric) | 500 |
Maximum number of servers per server group | 20 |
Maximum number of servers per cluster | 8 |
| Deployment Option | Icon |
|---|---|
CloudHub 2.0 |
|
CloudHub |
|
Hybrid |
|
Anypoint Platform Private Cloud Edition |
|
Anypoint Runtime Fabric |
|
| Deployment Option | Implementation | More Information |
|---|---|---|
CloudHub 2.0 | Via clustering with two or more replicas and Anypoint VPN. | |
CloudHub | Via clustering with two or more workers and Anypoint VPN. | CloudHub High Availability Features |
Hybrid | Via server groups or clusters. Clustered Mule instances have distributed shared memory, which provides persistent VM queues, transactions, and cluster-wide data storage. | Server Groups |
Private Cloud Edition | Via server groups or clusters. Clustered Mule instances have distributed shared memory, which provides persistent VM queues, transactions, and cluster-wide data storage. | Server Groups |
Runtime Fabric | Via automatic application fail-over. You obtain high availability when you deploy two or more replicas per application. |
| Deployment Option | Version | More Information |
|---|---|---|
CloudHub 2.0 | Java 8, Java 17 | CloudHub 2.0 Runtime and Infrastructure Patch Update Release Notes |
CloudHub | Java 8, Java 17 | CloudHub Runtime and Operating System Patch Update Release Notes |
Hybrid | See the Mule runtime engine release notes to determine the minimum supported Java version. | |
Private Cloud Edition | See the Mule runtime engine release notes to determine the minimum Java supported version. |
| Deployment Option | Supported Load Balancing | Alternative/Workaround |
|---|---|---|
CloudHub 2.0 | When deploying your application to two or more replicas, the CloudHub HTTP load balancing service distributes requests across these replicas. See Scale Out and Data Center Redundancy. | |
CloudHub | If your application runs on multiple workers, the CloudHub shared load automatically balances incoming traffic. See Dedicated Load Balancers. | Use the optional dedicated load balancer (DLB) component to route external traffic to multiple Mule applications deployed to CloudHub workers in Anypoint Virtual Private Cloud (VPC). |
Hybrid | Not Supported. | You can manage load balancing with the tools connected to your on-premises resources. |
Private Cloud Edition | Not Supported. | You can manage load balancing with the tools connected to your on-premises resources. |
Runtime Fabric | Internal load balancer for basic load balancing. | You can also forward logs from Runtime Fabric to a rsyslog server. |
| Deployment Option | Description | Alternative/Workaround | More Information |
|---|---|---|---|
CloudHub 2.0 | CloudHub 2.0 provides access to log data that includes deployment messages and events for each replica and Mule runtime engine logs. | ||
CloudHub | CloudHub provides a logging service for customizing log levels, searching logs, and downloading logs. | ||
Hybrid | The Runtime Manager logging feature is not available for hybrid deployments. | You can configure on-premises applications to send data to external analytics tools, such as Splunk or ELK, to manage your logs. | Export Data from Runtime Manager to External Analytics Tools |
Private Cloud Edition | The Runtime Manager logging feature is not available for hybrid deployments. | The Runtime Manager logging feature is not available for hybrid deployments. | Export Data from Runtime Manager to External Analytics Tools |
Runtime Fabric | Runtime Fabric supports Anypoint Monitoring. | You can also forward logs from Runtime Fabric to a rsyslog server. |
| Deployment Option | Implementation | Functionality | More Information |
|---|---|---|---|
CloudHub 2.0 | - You can create alerts in Runtime Manager for applications deployed to CloudHub 2.0. | - Run thread dumps. Configure application alerts. | - Monitoring Apps Deployed to CloudHub 2.0 |
CloudHub | Runtime Manager dashboards provide performance metrics for all deployed applications. | Alerts based on alert conditions on deployed applications. Standard notifications to inform you when events occur in your applications. Add a CloudHub connector to your application’s flows and set up custom alerts and notifications triggered by any event. | |
Hybrid | Runtime Manager dashboards provide performance metrics for all deployed applications. | Alerts based on alert conditions on deployed applications. Standard notifications to inform you when events occur in your applications. Alerts triggered by events related to the servers on which they run. | |
Private Cloud Edition | Anypoint Platform PCE does not support Runtime Manager dashboards. | Alerts based on alert conditions on deployed applications. Standard notifications to inform you when events occur in your applications. Alerts triggered by events related to the servers on which they run. | |
Runtime Fabric | - The Runtime Fabric agent monitors Kubernetes Deployments labelled with | When Kubernetes updates the state of the deployment, the agent sends that update to the control plane. | - Monitoring Application Deployments |
| Deployment Option | Implementation | Note | More Information |
|---|---|---|---|
CloudHub 2.0 | You do not need to configure your applications to use Object Store in CloudHub 2.0. Additionally, Mule 4 applications support Object Store v2, which can be enabled from Anypoint Runtime Manager console. | When you enable Object Store v2 in CloudHub 2.0, note that it is rate limited. | |
CloudHub | CloudHub provides a preconfigured default object store that you can reference using Anypoint Connector for Object Store. | Idempotent routers work only with in-memory stores. | |
Hybrid | Not available for hybrid deployments. | To use object stores, you must configure a database to store data. | |
Private Cloud Edition | Not available for Anypoint Platform PCE deployments. | To use object stores, you must configure a database to store data. | |
Runtime Fabric | Not available for Runtime Fabric deployments. | To use object stores, you must configure a database to store data. |
| Deployment Option | Implementation | Note | More Information |
|---|---|---|---|
CloudHub 2.0 | You can use Runtime Manager to view and control the Scheduler components within the flows in your deployed applications without changing your running application. | To view the application schedules, you must have the Exchange Viewer permission, in addition to the Read Applications permission. | |
CloudHub | You can use Runtime Manager to view and control the Scheduler components within the flows in your deployed applications. | You cannot manage CloudHub schedules using scripts. Use the Schedules tab or the CloudHub API to manage CloudHub schedules. | |
Hybrid | Not available for hybrid deployments. | To schedule tasks, use the Scheduler endpoint element in your flows. | |
Private Cloud Edition | Not available for Anypoint Platform PCE deployments | To schedule tasks, use the Scheduler endpoint element in your flows. | |
Runtime Fabric | Not available for Runtime Fabric deployments. | To schedule tasks, use the Scheduler endpoint element in your flows. |
| Deployment Option | Implementation | More Information |
|---|---|---|
CloudHub 2.0 | CloudHub 2.0 regularly applies security patches as needed to ensure that your application is secure. | |
CloudHub | CloudHub applies security patches as needed to ensure that your application is secure and, once per month, it updates Mule to maintain the stability of your application. | |
Hybrid | After an application is deployed and running, you must apply any security updates for the selected runtime version manually. | |
Private Cloud Edition | After an application is deployed and running, you must apply any security updates for the selected runtime version manually. | |
Runtime Fabric | When a security update is available for the runtime version for an app, you can see and apply the update in Runtime Manager. |
| Deployment Option | Implementation | More Information |
|---|---|---|
CloudHub 2.0 | A shared space is an elastic cloud of resources that includes Mule instances running in a multi-tenant environment. CloudHub 2.0 provides one shared space in each supported region, to which you deploy your integration applications. | |
CloudHub | Each application deployed to CloudHub runs on a separate virtual server. You don’t need to use domains to share ports or other resources between applications. | |
Hybrid | When deploying on-premises, you can create | |
Private Cloud Edition | When deploying on-premises, you can create |
| Deployment Option | Implementation |
|---|---|
CloudHub 2.0 | Use the MuleSoft diagnostics agent to troubleshoot your Mule applications deployed to CloudHub 2.0. This feature leverages Einstein generative AI to automate diagnostics collection and provide intelligent, actionable insights. See Generating Apps Diagnostics and Analyzing with Einstein. |
CloudHub | - The Insight troubleshooting tool provides in-depth visibility into business transactions and events on your Mule applications deployed through Runtime Manager. You can enable the Insight analytics feature and specify metadata options on the Insight tab. |
Hybrid | The Insight troubleshooting tool provides in-depth visibility into business transactions and events on your Mule applications deployed through Runtime Manager. |
Private Cloud Edition | Anypoint Platform PCE does not include the Insight troubleshooting tool. |
Runtime Fabric | Use Anypoint Monitoring to view information about applications deployed to Runtime Fabric. To obtain the health status of the cluster and components, use Runtime Fabric command-line tools. See Monitoring Applications Deployed to Runtime Fabric. |
| NOTIFICATIONS | MULE TYPE | NONE | BE | TRACKING | DEBUG |
|---|---|---|---|---|---|
Pipeline Message | PipelineMessageNotifications | √ | √ | √ | |
Async Message | AsyncMessageNotifications | √ | √ | √ | |
Exception | ExceptionStrategyNotifications | √ | √ | √ | |
Event | EventNotifications | √ | √ | √ | |
Exception Strategy | ExceptionStrategyNotifications | √ | √ | ||
Transaction | TransactionNotifications | √ | √ | ||
Endpoint Message | EndpointMessageNotifications | √ | √ | ||
Message Processor | MessageProcessorNotification | √ | |||
Component Message | ComponentMessageNotifications | √ |
| Replay Level Option | Description |
|---|---|
| Specifies to not store any data related to message replay and to disable the replay feature for these flows. |
| Stores messages for replay for only those flows in the Mule app that start with a message source. |
| Stores messages for replay for every flow in the Mule app. |
| Tracked Flow Option | Description |
|---|---|
| The name of the flow, as it is coded in the Mule app XML configuration file. |
| One of the values |
| One of the values |
| Whether to also store the message payload for replay, or to just store the message metadata (if |
| Field | Description | Default Value |
|---|---|---|
Username (Required) | Username to connect to Splunk | |
Password (Required) | Password associated with the Splunk username | |
host (Required) | IP address or hostname of the server where Splunk is running | |
port | Splunk management port | 8089 |
protocol | Protocol for the connection to the Splunk management port Possible values are http, https, and tcp. | https |
SSL Protocol (REST API only) | SSL Security Protocol to use for the HTTPS connection Possible values are TLSv1_2, TLSv1_1, TLSv1, and SSLv3. | TLSv1_2 |
Splunk Index | Name of the Splunk index to send all events to If the index doesn’t exist, the internal handler creates it if the permissions associated with the username are adequate. | main |
Splunk Source | The source used for events sent to Splunk | mule-events |
Splunk Type | The source type used for events sent to Splunk | mule |
Date Format | Date format to use to format the timestamp | yyyy-MM-dd’T’HH:mm:ssSZ |
* Implementations of this interface provides new functionality to the Runtime Manager agent. These services handle data from * Mule and interact with Mule. *
* * @see com.mulesoft.agent.handlers.ExternalMessageHandler , InternalMessageHandler * @since 1.0 */ public interface MuleAgentService extends Switcher { public List* Gets messages coming from an external system and executes {@link com.mulesoft.agent.services.MuleAgentService} based * the request. *
** This is just a marker interface for the communication layer to recognize the interface as a External message receiver *
* * @since 1.0 */ public interface ExternalMessageHandler extends Switcher { } ``` ### Internal Message Handler ```java /** ** Internal messages come generally from mule side. {@link InternalMessageHandler} are use to handle those messages depending on, * for example, the transport. *
* * @param* Process an internal message *
* * @param message The message to be processed * @return true if the message could be processed */ boolean handle(@NotNull Rq message); } ``` ### Switcher ```java /** ** All the classes implementing this interface will be able to enable/disable themselves *
* * @since 1.0 */ public interface Switcher { /** *
* Turn the feature on, the class will be behave as expected
*
* If the feature is being disabled, any resources it has allocated should be freed and taken again when it is reenabled
*
* Check the state of the class *
* * @return true if it is on, false otherwise */ boolean isEnabled(); } ``` --- product: Runtime Manager keywords: cloudhub, analytics, monitoring, insight, flow manager, flow management, start flow, stop flow --- # Flow Management > For the full documentation index, see: https://docs.mulesoft.com/llms.txt [Hybrid](deployment-strategies#hybrid-deployments)[ Private Cloud Edition](deployment-strategies#anypoint-platform-private-cloud-edition) You can individually start and stop the specific flows within your deployed applications via the Runtime Manager UI. All flows are active by default. The flow management feature isn’t available for apps deployed to CloudHub and Anypoint Runtime Fabric. To act on flows, you must have **Manage Applications** permission on the desired applications. ## Start and Stop Flows Individual flows can be set to active or inactive through the **Start** and **Stop** buttons. Select one or more flows in your app, and click the **Start** or **Stop** button.  > [!NOTE] Starting a flow doesn’t imply triggering its endpoints, it just makes it active if > previously set inactive. ## Set Flows to Unmanaged In some cases, you can explicitly set up your applications to start and stop flows automatically according to any criteria you want. In these cases, this behavior is carried out by logic in the applications running inside Mule runtime itself, and Runtime Manager is unaware of the logic behind these changes. The default flow status for every application is unmanaged. This means that your flows freely transition states between active and inactive according to the behavior set up in application logic running in Mule runtime. You can click **Start** or **Stop** for a flow in the **Flow Management** tab to override the unmanaged status. In this case, Runtime Manager continually enforces the active or inactive state of the flow, regardless of any changes Mule runime attempts. Click **Unmanage** to reset the flow status to unmanaged at any time.  ## See Also - [Flow Metrics](https://docs.mulesoft.com/runtime-manager/flow-metrics) - [Manage Deployed Applications](https://docs.mulesoft.com/runtime-manager/managing-deployed-applications) - [Manage Applications on Your Servers](https://docs.mulesoft.com/runtime-manager/managing-applications-on-your-own-servers) - [Monitor Applications](https://docs.mulesoft.com/runtime-manager/monitoring) --- product: Runtime Manager keywords: cloudhub, analytics, monitoring, insight, filter --- # Flow Metrics > For the full documentation index, see: https://docs.mulesoft.com/llms.txt [CloudHub 2.0](deployment-strategies#cloudhub-2-0)[ CloudHub ](deployment-strategies#cloudhub)[ Hybrid ](deployment-strategies#hybrid-deployments)[ Private Cloud Edition](deployment-strategies#anypoint-platform-private-cloud-edition) > [!IMPORTANT] MuleSoft deprecated the flow metrics feature on Dec 9th, 2019. We recommend that you > use [Anypoint Monitoring](https://docs.mulesoft.com/monitoring/) to monitor your applications and APIs. You can view the evolution of performance metrics for individual flows in your applications that are deployed to servers on premises (hybrid or Anypoint Platform Private Cloud Edition). ## Enable Flow Metrics for Hybrid When you deploy a new application to a hybrid deployment environment, the flow metrics feature is not enabled by default. To enable flow metrics, your account must be granted one of the following permissions. - **Manage Application Data** - **Create Applications** - **Manage Settings** To enable flow metrics: 1. From Runtime Manager, click **Applications**. 2. Select the application where you want to enable flow metrics, then click **Manage Application**. 3. Click **Settings**, then select the **Flow Monitoring** tab.  4. Select **Enabled**. 5. Click **Apply Changes**. ## Access Flow Metrics To view flow metrics, you must have the Read Application permission for the desired applications. 1. Select the **Applications** tab in Runtime Manager. 2. Enter a running application’s settings (either by clicking the **Manage Application** button on the side panel, or the application name itself in the table). 3. Select the **Flows** tab on the left side bar. 4. Select one or multiple flows.  ## Verify the Status of Servers If your application is deployed to a cluster or a server group, you can view the status of the flow on each server it runs in.  Use this information to rule out the possibility of a communication issue leading to inconsistent states throughout the servers. ## View Flow Metrics Once you have selected one or multiple flows, you can view the **Metrics** tab.  This tab contains charts for the following three metrics: - Mule messages - Errors - Flow response time All metrics are displayed as an average relative to the selected time scale. > [!NOTE] The retention period for flow metrics is two weeks. ## Navigate the Metrics All graphs can be viewed at different time scales by selecting the desired time interval on the top-right corner.  If your application runs on a cluster or server group, the aggregated metrics of the entire set of servers included are charted as a single plot line. By hovering your mouse over a given point of a graph, an overlay displays numerical detail about activity on that instant.  You can set up alerts to notify you automatically whenever any of these metrics hits a critical value for a sustained period of time. ## See Also - [Anypoint Monitoring](https://docs.mulesoft.com/monitoring/) - [Alerts](https://docs.mulesoft.com/runtime-manager/alerts-on-runtime-manager) - [Insight](https://docs.mulesoft.com/runtime-manager/insight) - [Flow Management](https://docs.mulesoft.com/runtime-manager/flow-management) - [Monitor Applications](https://docs.mulesoft.com/runtime-manager/monitoring) --- product: Runtime Manager keywords: cloudhub, analytics, monitoring, insight, filter --- # Insight (To be Deprecated) > For the full documentation index, see: https://docs.mulesoft.com/llms.txt [CloudHub](deployment-strategies#cloudhub)[ Hybrid](deployment-strategies#hybrid-deployments) This page documents a legacy troubleshooting tool for Mule apps deployed to CloudHub and on-premises servers. For the new troubleshooting approach with traces, refer to these pages: [Enable Trace Data Collection for CloudHub Apps](#enable-trace-data) and [Enable Trace Data Collection for Hybrid Runtime Servers](https://docs.mulesoft.com/monitoring/am-installing#tracing-setup). Insight is a troubleshooting tool that provides in-depth visibility into business transactions and events on your Mule apps deployed to CloudHub and on-premises servers. Insight tracks everything your data does in an app so you can find and recover from errors that occur during message processing. Replay is not supported for free or trial user accounts. > [!IMPORTANT] Enabling Insight can significantly impact data processing performance and memory > consumption. For this reason, do not enable Insight for long periods for production environments. > > Use Insight only for troubleshooting specific transactions by searching for a transaction ID or a > unique text string. > > For information about tools to use for monitoring a production environment, see > [Monitor Applications and Servers](https://docs.mulesoft.com/runtime-manager/monitoring). The Insight dashboard enables you to view events that occur within the flows that handle your business transactions. You can drill down into event-related data to analyze the root cause of failures, isolate performance bottlenecks, and test for compliance with company procedures. Insight helps you answer questions about your integrated apps, such as: - What happened with a particular transaction or synchronization? - When did the transaction occur? How long did it take? - What was the result of a transaction? - If something went wrong during processing, at what point did the failure occur? After you enable Insight, the following items are tracked by default: - Data passing through endpoints (inbound and outbound) in your Mule applications - Flow initiation and completion - Custom business events that you embed in your Mule flows ## Limits and Limitations The following limits and limitations apply when using Insight: - Insight drops events over the following limits: - A single application is limited to 50,000 events per minute. - All applications in a single business group are limited to 100,000 events per minute. - Insight stores no more than 20 custom event definitions per application definition. - Insight does not support long-running processes that contain more than 10,000 events in a single transaction. For this reason, Insight might not provide visibility into batch processing. See [Batch Processing](https://docs.mulesoft.com/mule-runtime/latest/batch-processing-concept). - Insight does not preserve replay data when switching regions. Ensure that this limitation doesn’t violate your compliance requirements. - Logs for applications deployed to on-premises servers contain event information but not message contents. - Insight returns consistent results only when searching for terms that are an exact match. Because Insight limits the number of terms that are included in a query, it might not find all matches when searching for a pattern. To work around this limitation, either: - Search for an exact transaction ID. - Tag transactions with custom business events, and then search for transactions based on the custom business events. See [Set Up Business Events](#set-up-business-events). ### Data Persistence Insight does not limit the size of transactions. Insight displays all transactions in your application for 30 days and keeps events for two days. ### Payload Transformation The following MIME types are always mapped as Strings: ```linenums application/javascript application/json application/csv application/rtf application/vnd.mozilla.xul+xml application/x-csh application/x-sh application/xml application/xml+html images/svg+xml text/calendar text/css text/csv text/html text/plain text/xml ``` For all other types, Mule agent attempts to transform payloads to another format, based on the Stream type that Mule runtime engine exposes to the Mule agent. For example, Mule agent converts `CURSOR_STREAM_PROVIDER` payloads to a byte array. Any streams that are not mapped to String by default appear in the logs. ## Enable or Disable Insight To enable Insight to track the events your Mule servers generate: 1. Sign in to your Anypoint Platform account. 2. Click **Runtime Manager**. 3. Click **Applications** in the menu on the left, and click the application in the **Name** column to open the management panel on the right side of the page. 4. In the management panel, click **Insight**. 5. Click **Settings** in the menu on the left, and then click the **Insight** tab:  Figure 1. The arrow shows the **Insight** tab on the **Settings** page. 6. Select one of the tracking options: - **Disabled** to disable Insight - **Metadata** to track only events - **Metadata and Replay** to track events and enable the ability to instantly replay a transaction from the console The **Metadata and Replay** option is unavailable for free or trial user accounts. For more information, see [Diagnose Problems and Replay Transactions](#diagnose-problems-and-replay-transactions). 7. Select the checkbox to confirm that you want to enable Insight, and click **Apply Changes**. 8. Click **Apply Changes** to save the application settings. ## Search and Filter Transactions and Events The Insight dashboard displays information at three tracking levels: - **Transactions** Logical groupings of related events that often correspond to a business view of the system - **Events** Low-level details of a transaction Events map to message processors and endpoints and reveal information about exceptions and any custom business events you might have configured. - **Metadata** Customized key-value pairs that you specify as part of custom events in your application The detail that Insight tracks at this level provides information about high-level business events. The following image shows where to find transactions, events, and metadata on the Insight dashboard:  Figure 2. The screenshot shows (**1**) the Transactions level, (**2**), the Events level, and (**3**), the Metadata level on the Insight dashboard. Business data, if configured, appears in the Metadata area (**3**) of the dashboard. See [Set Up Business Events](#set-up-business-events). ### Search or Filter Transactions On the **Insight** page, you can search or filter data to refine the results displayed. You can search for: - A specific transaction by transaction ID - Transactions within a specific date range - Transactions according to exact flow name, exact exception message, processing time, and any custom business data To enable the **Business Data** field your app must have business events configured. See [Set Up Business Events](#set-up-business-events). To search or filter transactions: 1. Click **Insight** in the menu on the left. 2. Enter your search criteria in the **Search** field. 3. Click **Advanced** in the **Search** field. 4. Specify filter options:  Figure 3. The screenshot shows the advanced search filter fields on the Insight dashboard. - To display only failed or completed transactions, select **Failed** or **Completed** from the menu in the **Transaction ID** field:  Figure 4. The arrow shows the menu in the **Transaction ID** field. - To display transactions within a specific date range, specify a date or range in the **Date & Time** fields. Alternatively, drag within the graph to select a specific date range:  Figure 5. The arrow shows the selected transaction range on the Insight dashboard. 5. Click **Apply** on the **Advanced** pane to apply your search criteria. 6. If you want to save a search, click **Save search**:  Figure 6. The arrow shows the **Save search** icon on the Insight dashboard. Runtime Manager saves the search to the name you specify. After you save a search, you can: - Run a saved search by clicking the search name. - Edit a saved search by hovering over the search name and click the **Edit** link:  Figure 7. The arrow shows the saved search being edited. Click **Done** to save your changes. - Delete a saved search by clicking the **Edit** link, and then clicking the delete icon (trash can) to the right of the search name. ### Filter Events You can refine the types of events that Insight displays for each transaction. When debugging, you might find it useful to see all events so that you can drill down into the detailed steps of your flow. If you want to analyze higher-level business information, you can apply a filter to view only your custom business events. To display the filter options, click the **Transaction details** menu for a transaction:  Figure 8. The arrow shows the **Transaction details** menu. The default settings of the events filter depend upon your user role: - **Support** The default events filter setting displays only custom events. - **Admin** or **Developer** The default events filter setting displays custom events, endpoint events, and message processor events, but does not display flow events. ## Diagnose Problems and Replay Transactions When Insight reports a failed transaction, you can diagnose the problem and fix the root issue. ### Transaction Failed Status For example, when a transaction fails because an application exceeds the limited number of API calls for a Salesforce account, Insight displays the status of the transaction as `Failed`. Click to expand the transaction, and then examine the individual events within that transaction. The exception and the error message are listed next to the failed event, as well as an existing stack trace:  ### Replay Transaction [](deployment-strategies#cloudhub-deployments) After investigating the logs and resolving the issue (for example, by purchasing more API capacity) that caused the transaction failure, you can replay the transaction. Replay is not available for free or trial user accounts. 1. Click the replay transaction icon  to the right of the first event in the failed transaction to replay it:  Figure 9. The screenshot shows (**1**) the replay transaction icon and (**2**) the **Purge Replay Data** button. 2. At the prompt, click **Replay Transaction** to confirm. Insight displays an information popup indicating that the transaction was replayed and displays the replayed transactions immediately on the dashboard and in the **Logs** tab. ### Purge Replay Data [](deployment-strategies#cloudhub-deployments) To delete all existing replay data for that application, click the **Purge Replay Data** button. > [!WARNING] You can’t restore replay data that has been purged. ## Table of Insight Status States The following table describes the status states that Insight reports:| Status | Description |
|---|---|
| The event failed while being processed and has an associated exception. |
| The event processed fully and successfully. |
| The event has started and has not yet completed. |
| The event has been put on hold due to exceeding the maximum number of events to be processed per transaction (10000). Any event above this number is set as stalled and then processed after the number of events to be processed is no longer exceeded. |
| If a transaction can’t finish within 24 hours, the events with |
| Mule version | Runtime Manager Agent version | Java version |
|---|---|---|
4.3.0 | 2.4.3 or later | 8 |
4.4.0 | 2.4.27 or later | 8 |
4.4.0 | 2.4.28 or later | 8,11 |
4.5.0 | 2.5.6 or later | 8,11 |
4.6.0 | 2.6.0 or later | 8,11,17 |
| Parameter | Value | Description |
|---|---|---|
| Displays help for the command on the command line. | |
| Updates the agent, preserving the existing When you update a previous agent installation using -U, you can’t include other parameters on the command line. | |
| Encrypts the passwords in an existing Use this option alone to encrypt passwords. For information, see Encrypt Passwords in an Existing mule-agent.yml File. | |
| Decrypts the passwords in an existing Use this option alone to decrypt passwords. For information, see Update the Main Password and Display Passwords in mule-agent.yml in Plain Text. | |
|
| Specifies the location of the Use this option if you are running the installation script from a location other than The amc_setup script reads the |
| Skips configuration of the API gateway | |
| Configures the agent to use an unencrypted REST connection. Do not use this parameter with the PCE This option replaces the contents of | |
| Configures the agent to establish a TLS connection with an on-premises administration console. Do not use this parameter with the PCE This option replaces the contents of | |
|
| Configures the agent to connect with either Anypoint Platform PCE or cloud-based Anypoint Platform managed by MuleSoft.
|
|
| Specifies the proxy configuration to use when registering with the connection. |
|
| Specifies the region to deploy to. Available regions are |
| Enables FIPS 140-2 compliance on Mule 4 runtime on *nix-based servers. |
| Parameter | Value | Description |
|---|---|---|
|
| Specifies the service location URL of your local instance of Runtime Manager, for example, You can test whether the service is available at |
|
| Specifies the service location URL of your local instance of MCM, for example, You can test whether the service is available at |
|
| Specifies the service location URL of your local instance of Access Management, for example, You can test whether the service is available at |
|
| Specifies the service location (URL) of your local instance of Contract Caching Service, for example, |
|
| Specifies the service location URL of your local instance of API Manager, for example, You can test whether the service is available at |
|
| Specifies the service location URL of your Auth Proxy, for example, |
| Field | Description | Default value |
|---|---|---|
| Buffer type. Valid values are | |
| Number of retries after an exception was thrown in the flush method. | |
| Maximum number of events to keep in buffer. | |
| Frequency at which the flush method will run, in milliseconds. | |
| Path to the buffer file. Only valid for buffers of type |
|
| Strategy to follow when the buffer is exhausted. If not specified, the buffer will grow automatically. Valid values are | N/A |
| Number of threads used by the FlushThreadExecutor when the buffer is exhausted and the strategy defined by |
|
| If true, messages will not be returned to the buffer if the flush is not successful. |
|
| Key | Description |
|---|---|
| Required. |
| Required. A validator type can have multiple implementations. The name for the |
| Optional. Set to |
| Key | Description |
|---|---|
| Optional. The truststore filename that contains one or more certificates used to validate the signature of all JAR files that you use for deployments. The default location is |
| Optional. |
| Optional. Each certificate stored in a truststore file is identified by an alias string. This property specifies a single alias used to validate all JAR files. If you don’t provide an alias, the validator uses all certificates in the truststore file to match the signature in the JAR files. |
| Optional for JKS, required for PKCS12. The truststore file password. |
| Icon | State | Description |
|---|---|---|
 |
| The application is not running. |
 |
| Application is in the process of transitioning to another state. |
|
| Application is running or the update succeeded. The Application shows Started when running on at least one of the Cluster nodes. |
|
| Application deployment failed. The cause of the failure appears in the console. |
 | Application update failed. |
| Icon | State | Description |
|---|---|---|
| Deleted | Application is deleted. |
| Applying | Application is in the process of transitioning to another state. |
| Applied | Application is running or the update succeeded. |
| Failed | Application deployment failed. The cause of the failure appears in the console. |
 | Unknown | Application’s status is unknown because the server is not responding to the platform (on-premises deployments only). |
| Icon | State | Description |
|---|---|---|
| Running | All nodes are running. |
| Running | At least one of the Cluster nodes is running. |
| Running with communication issue | All nodes are running, but communication issues exist between them. |
| Disconnected | All nodes are disconnected. |
| Created | A server/node is registered in the platform but is not started. |
| Graphs Display the Average, Minimum, and Maximum: | |||
|---|---|---|---|
Selected Time Range | Number of Mule Messages | Number of Errors | Response Time (milliseconds) |
3 Hours | Per minute | Per minute | Per minute |
24 Hours | Per 8 minutes | Per 8 minutes | Per 8 minutes |
7 Days | Per hour | Per hour | Per hour |
2 Weeks | Per 2 hours | Per 2 hours | Per 2 hours |
| Extension | Kind of document | MIME Type | Converted to String |
|---|---|---|---|
.epub | Electronic publication (EPUB) | application/epub+zip | FALSE |
.jar | Java Archive (JAR) | application/java-archive | FALSE |
.js | JavaScript (ECMAScript) | application/javascript | TRUE |
.json | JSON format | application/json | TRUE |
.doc | Microsoft Word | application/msword | FALSE |
.arc | Archive document (multiple files embedded) | application/octet-stream | FALSE |
.bin | Any kind of binary data | application/octet-stream | FALSE |
.ogx | OGG | application/ogg | FALSE |
Adobe Portable Document Format (PDF) | application/pdf | FALSE | |
.rtf | Rich Text Format (RTF) | application/rtf | TRUE |
.azw | Amazon Kindle eBook format | application/vnd.amazon.ebook | FALSE |
.mpkg | Apple Installer Package | application/vnd.apple.installer+xml | FALSE |
.xul | XUL | application/vnd.mozilla.xul+xml | TRUE |
.xls | Microsoft Excel | application/vnd.ms-excel | FALSE |
.ppt | Microsoft PowerPoint | application/vnd.ms-powerpoint | FALSE |
.odp | OpenDocument presentation document | application/vnd.oasis.opendocument.presentation | FALSE |
.ods | OpenDocument spreadsheet document | application/vnd.oasis.opendocument.spreadsheet | FALSE |
.odt | OpenDocument text document | application/vnd.oasis.opendocument.text | FALSE |
.vsd | Microsoft Visio | application/vnd.visio | FALSE |
.7z | 7-zip archive | application/x-7z-compressed | FALSE |
.abw | AbiWord document | application/x-abiword | FALSE |
.bz | BZip archive | application/x-bzip | FALSE |
.bz2 | BZip2 archive | application/x-bzip2 | FALSE |
.csh | C-Shell script | application/x-csh | TRUE |
.rar | RAR archive | application/x-rar-compressed | FALSE |
.sh | Bourne shell script | application/x-sh | TRUE |
.swf | Small web format (SWF) or Adobe Flash document | application/x-shockwave-flash | FALSE |
.tar | Tape Archive (TAR) | application/x-tar | FALSE |
.xhtml | XHTML | application/xhtml+xml | TRUE |
.xml | XML | application/xml | TRUE |
.zip | ZIP archive | application/zip | FALSE |
.aac | AAC audio file | audio/aac | FALSE |
.mid .midi | Musical Instrument Digital Interface (MIDI) | audio/midi | FALSE |
.oga | OGG audio | audio/ogg | FALSE |
.weba | WEBM audio | audio/webm | FALSE |
.wav | Waveform Audio Format | audio/x-wav | FALSE |
.ttf | TrueType Font | font/ttf | FALSE |
.woff | Web Open Font Format (WOFF) | font/woff | FALSE |
.woff2 | Web Open Font Format (WOFF) | font/woff2 | FALSE |
.gif | Graphics Interchange Format (GIF) | image/gif | FALSE |
.jpeg .jpg | JPEG images | image/jpeg | FALSE |
.svg | Scalable Vector Graphics (SVG) | image/svg+xml | TRUE |
.tif | .tiff Tagged Image File Format (TIFF) | image/tiff | FALSE |
.webp | WEBP image | image/webp | FALSE |
.ico | Icon format | image/x-icon | FALSE |
.ics | iCalendar format | text/calendar | TRUE |
.css | Cascading Style Sheets (CSS) | text/css | TRUE |
.csv | Comma-separated values (CSV) | text/csv | TRUE |
.htm | .html HyperText Markup Language (HTML) | text/html | TRUE |
.txt | Plain Text | text/plain | TRUE |
.3gp | 3GPP audio/video container | video/3gpp audio/3gpp if it doesn’t contain video | FALSE |
.3g2 | 3GPP2 audio/video container | video/3gpp2 audio/3gpp2 if it doesn’t contain video | FALSE |
.mpeg | MPEG Video | video/mpeg | FALSE |
.ogv | OGG video | video/ogg | FALSE |
.webm | WEBM video | video/webm | FALSE |
.avi | AVI: Audio Video Interleave | video/x-msvideo | FALSE |
Multipart | "multipart/mixed, multipart/alternative, multipart/digest multipart/parallel" | FALSE |
| Region | Name | Port |
|---|---|---|
US | anypoint.mulesoft.com | 443 |
US | runtime-manager.anypoint.mulesoft.com | 443 |
US | analytics-ingest.anypoint.mulesoft.com | 443 |
US | data-authenticator.anypoint.mulesoft.com | 443 |
US | exchange-files.anypoint.mulesoft.com | 443 |
US | exchange2-asset-manager-kprod.s3.amazonaws.com | 443 |
US | us1.ingest.mulesoft.com | 8443 |
US-GOV | runtime-manager.gov.anypoint.mulesoft.com | 443 |
US-GOV | data-authenticator.gov.anypoint.mulesoft.com | 443 |
US-GOV | gov.anypoint.mulesoft.com | 443 |
US-GOV | exchange-files.gov.anypoint.mulesoft.com | 443 |
US-GOV | exchange2-asset-manager-kgprod.s3.us-gov-west-1.amazonaws.com | 443 |
EU | eu1.anypoint.mulesoft.com | 443 |
EU | runtime-manager.eu1.anypoint.mulesoft.com | 443 |
EU | analytics-ingest.eu1.anypoint.mulesoft.com | 443 |
EU | data-authenticator.eu1.anypoint.mulesoft.com | 443 |
EU | exchange2-asset-manager-kprod-eu.s3.eu-central-1.amazonaws.com | 443 |
EU | eu1.ingest.mulesoft.com | 8443 |
| Region | Name | IP Address |
|---|---|---|
US | runtime-manager.anypoint.mulesoft.com | 18.214.68.14 |
US | runtime-manager.anypoint.mulesoft.com | 35.174.151.175 |
US | runtime-manager.anypoint.mulesoft.com | 18.213.137.40 (Starting Feb 2024) |
US | runtime-manager.anypoint.mulesoft.com | 34.232.255.44 (Starting Feb 2024) |
US | runtime-manager.anypoint.mulesoft.com | 44.209.29.79 (Starting Feb 2024) |
| Region | Name | IP Address |
|---|---|---|
EU | runtime-manager.eu1.anypoint.mulesoft.com | 18.185.141.77 |
EU | runtime-manager.eu1.anypoint.mulesoft.com | 3.123.216.217 |
EU | runtime-manager.eu1.anypoint.mulesoft.com | 3.127.253.183 (Starting Feb 2024) |
| Region | Hostname |
|---|---|
US | anypoint.mulesoft.com |
US | analytics-ingest.anypoint.mulesoft.com |
US | data-authenticator.anypoint.mulesoft.com |
US | us1.ingest.mulesoft.com |
US-GOV | runtime-manager.gov.anypoint.mulesoft.com |
US-GOV | data-authenticator.gov.anypoint.mulesoft.com |
US-GOV | gov.anypoint.mulesoft.com |
EU | eu1.anypoint.mulesoft.com |
EU | analytics-ingest.eu1.anypoint.mulesoft.com |
EU | data-authenticator.eu1.anypoint.mulesoft.com |
EU | eu1.ingest.mulesoft.com |
| URL | Description |
|---|---|
runtime-manager.anypoint.mulesoft.com | Connection for ARM management capabilities (public-cert agents) |
data-authenticator.anypoint.mulesoft.com | Connection to the metrics ingestion service of arm-monitoring stack (public-cert agents) |
| Field | Description |
|---|---|
| Contains the following itemized information about the application:
For a list of all possible application states, see the Application States and Deployment Status section. |
| Current status of the deployment. After a deployment operation is completed, the message remains as For a list of all possible status messages, see the Application States and Deployment Status section. |
| An informational message about the current deployment stage. In case of a deployment failure, information about the reason for the failure is included in the message. |
| Field | Description |
|---|---|
| Contains the following itemized information about the domain:
|
| Current status of the deployment. After a deployment operation is completed, the message remains as For a list of all possible status messages, see the Application States and Deployment Status section. |
| An informational message about the current deployment stage. In case of a deployment failure, information about the reason for the failure is included in the message. |
| Command | Description |
|---|---|
Downloads a standalone application artifact binary | |
Copies a standalone application | |
Deletes a standalone application | |
Deploys or redeploys an application to an on-premises server, server group, or cluster | |
Shows detailed information for a standalone application | |
Lists all standalone applications in the environment | |
Changes a standalone application artifact | |
Restarts a standalone application | |
Starts a standalone application | |
Stops a standalone application |
| Flag | Description | Example |
|---|---|---|
| Specifies the number of results to retrieve |
|
| Offsets the number of applications passed |
|
| Specifies the response format. |
|
| Flag | Description | Example |
|---|---|---|
| Stores message metadata of every Mule transaction. |
|
| Sets the logging level and scope pair:
To set multiple logging levels, provide multiple |
|
| Command | Description |
|---|---|
Creates new alert for standalone runtime | |
Describes an alert | |
Lists all alerts for standalone runtimes in the environment | |
Modifies alert for standalone runtime |
| Flag | Description | Example |
|---|---|---|
| Alert trigger condition |
|
| Alert notification email body |
|
| Email address to send alert notification to |
|
| Condition operator explaining values relation to threshold. |
|
| Condition duration in minutes |
|
| Username to send alert notification to |
|
| Alert resource ID. If not provided alert triggers for all resources. Depending on |
|
| Alert resource type |
|
| Alert severity |
|
| Alert notification email subject |
|
| Condition threshold number |
|
| Flag | Description | Example |
|---|---|---|
| Alert trigger condition |
|
| Alert notification email body |
|
| Email address to send alert notification to |
|
| Alert name |
|
| Condition operator explaining values relation to threshold. |
|
| Condition duration in minutes |
|
| Username to send alert notification to |
|
| Alert resource ID. If not provided alert triggers for all resources. Depending on |
|
| Alert resource type |
|
| Alert severity |
|
| Alert notification email subject |
|
| Condition threshold number |
|
| Command | Description |
|---|---|
Describes server | |
Deletes server | |
Changes an standalone application artifact | |
Modifies server | |
Gets server registration token. This token needs to be used to register a new server |
| Command | Description |
|---|---|
Adds server to a server group | |
Creates server group from servers | |
Describes server group | |
Deletes server group | |
Lists all server groups in the environment | |
Modifies server group | |
Removes server from a server group |
| Command | Description |
|---|---|
Adds server to cluster | |
Creates new cluster | |
Describes server cluster | |
Deletes cluster | |
Modifies cluster | |
Lists all clusters in the environment | |
Removes server from a cluster |
| Flag | Description | Example |
|---|---|---|
| Whether cluster should be multicast |
|
| Pair of server ID and IP address |
|
| Field | Data Type | Description | Type | Default Value |
|---|---|---|---|---|
| String | The JDBC driver to use to communicate with the database server | Required | |
| String | The JDBC URL for the database server | Required | |
| String | The username to use to connect to the database server | Required | |
| String | The password to use to connect to the database server | Required | |
| String | The name of the table in which the agent stores the events | Optional |
|
| Field | Data Type | Description | Type | Default Value |
|---|---|---|---|---|
| String | The JDBC driver to use to communicate with the database server | Required | |
| String | The JDBC URL for the database server | Required | |
| String | The username to use to connect to the database server | Required | |
| String | The password to connect to the database server | Required | |
| String | The name of the table in which the agent stores the events | Optional |
|
| String | The name of the table in which the agent stores the annotations associated with the main event | Optional |
|
| String | The name of the table in which the agent stores the custom business events associated with the main event | Optional |
|