Skip to content

configure-monitoring-cloudhub.adoc

Latest commit

 

History

History
115 lines (84 loc) · 5.08 KB

configure-monitoring-cloudhub.adoc

File metadata and controls

115 lines (84 loc) · 5.08 KB

Configure and Enable Anypoint Monitoring for Mule Apps (CloudHub)

To start monitoring Mule apps that are managed in CloudHub, you must deploy them to a supported version of Mule runtime engine and set the runtime version in your Mule app.

CloudHub 2.0: Anypoint Monitoring is enabled by default for Mule apps deployed to CloudHub 2.0.

Supported Versions of Mule Deployed to CloudHub

If you are not running a supported Mule runtime version, update the version in Runtime Manager.

Show me how

  • For new and existing Mule apps:

    1. Go to Settings in Runtime Manager for that app.

    2. Choose the new runtime from the Runtime Version selector.

      If you do not see a supported runtime version in the drop-down menu, scroll down to Show Old Patch Releases, click, and select a runtime for your app.

  • For Anypoint CLI deployments:

    If you are using the Anypoint CLI to deploy your Mule app (for example, through a build pipeline), you need to include the --runtime parameter with an appropriate value, for example:

    anypoint-cli --username="..." --password="..."
 --organization="Mythical, Inc"
 --environment="Production" runtime-mgr cloudhub-application deploy
 --runtime="3.9.4" helloworld ~/demoproj2.zip

  • For Maven deployments:

    If you are using Maven for deployment, you must modify the <muleVersion> tag in the pom.xml file. For example, you can change <muleVersion>3.9.3</muleVersion> to <muleVersion>3.9.4</muleVersion>).

reuse::partial$billing/pricing.adoc

Enable Monitoring by Default for New Apps

If you want your Mule apps to be monitored by default when you deploy them to CloudHub, configure this feature in Anypoint Monitoring before you deploy your apps. reuse::partial$billing/pricing.adoc

To configure automatic monitoring for each Mule app as it is deployed to CloudHub:

  1. In the Anypoint Monitoring navigation menu, click Settings:

  2. Select CloudHub.

  3. Select Enable Anypoint Monitoring for newly deployed CloudHub applications.

If you deployed Mule apps to CloudHub before you enabled this feature, you must enable monitoring for those apps manually. This feature does not retroactively enable monitoring for previously deployed apps.

Enable Monitoring for Apps Previously Deployed to CloudHub

You can enable monitoring for Mule apps running on non-AM versions of Mule in the Anypoint Monitoring Settings page, the application’s Settings page, or by using the Anypoint CLI for continuous integration and delivery (CI/CD).

For supported versions of Mule, see Configure Anypoint Monitoring for Mule Apps.

Enable Monitoring for an App in Monitoring Settings

Use the Settings page in Anypoint Monitoring to enable or disable monitoring for apps deployed to CloudHub and running on Mule:

  1. In the Anypoint Monitoring navigation menu, click Settings:

  2. Select CloudHub.

  3. In the Environment list, select the environment where the application is running.

    A list of running applications is shown for the selected environment.

    You can search for a specific application using the List of resources search box.

  4. Next to the application, click Enable to enable monitoring for the application.

Enable Monitoring for an App in Runtime Manager Settings

Enable monitoring for Mule apps running on supported versions of Mule by adding a property to an application deployed to CloudHub:

  1. Log in to Anypoint Platform.

  2. In the navigation bar or the main Anypoint Platform screen, click Runtime Manager.

  3. In the list of applications, select the application for which you want to enable monitoring. The application must be deployed to CloudHub and running on a supported version of Mule.

  4. In the navigation menu, click Settings.

  5. Click Properties, and add the following property:
    anypoint.platform.config.analytics.agent.enabled=true

    Runtime Manager application settings window with Properties tab selected

  6. Click Apply Changes.

Enable Monitoring using the Anypoint CLI

Use the Anypoint CLI and set the following property during your CI/CD deployment: anypoint.platform.config.analytics.agent.enabled=true

Performance Impact

Enabling Anypoint Monitoring can impact CPU utilization and memory utilization, which varies depending upon specific application behavior, such as inbound and outbound call rates. For a typical application, expected CPU utilization impact is less than 5%. For an accurate impact analysis specific to your application, test and estimate any performance impact in your pre-production environment prior to enabling monitoring in your production environment.
⚡