---
schema_version: "1"
id: 7a37f734167afbdae9537c5b79f4ad03bb4c897fad3176d2d5ef1536a3bd47f0
title: Anypoint Monitoring Agent Installer Release Notes
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/release-notes/monitoring/anypoint-monitoring-installer-release-notes.md
canonical_url: https://docs.mulesoft.com/release-notes/monitoring/anypoint-monitoring-installer-release-notes
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 83c21dccf2cf1050b2f0bef064878ff5e766cf14953cff88f8f2aa03d27ed41b
description: MuleSoft Documentation Site
latest: true
---
---
product: Release Notes
version: master
---

# Anypoint Monitoring Agent Installer Release Notes

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

These release notes are for patches made to the Anypoint Monitoring agent installer.

> [!NOTE] If you update the Runtime Manager agent, you must execute the Anypoint Monitoring agent
> uninstall script and then re-install the Anypoint Monitoring agent.

## August 19, 2026

**Version 3.2.18.11**

This 3.x version of the Anypoint Monitoring agent supports connections from apps in new cloud
regions.

To observe data from apps deployed to these regions, you must start with this version of the agent:

- [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 setup instructions, see
[Setting Up Monitoring for Hybrid Deployments](https://docs.mulesoft.com/monitoring/am-installing).

## June 26, 2026

**Version 3.2.18.3**

The 3.x version of the Anypoint Monitoring agent fixes an issue. Use of this version of the agent
requires your apps to run on Mule runtime version `>=` 4.4.0-20230522.

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Counts of inbound request metrics in Anypoint Monitoring custom dashboards and exported CSV data (<code>AnypointMonitoringExport.csv</code>) are now accurate.</p></div></div></td><td><div><div><p>W-22254890</p></div></div></td></tr><tr><td><div><div><p>For security purposes, this release updates SnakeYAML to version 2.0.</p></div></div></td><td><div><div><p>W-22933436</p></div></div></td></tr></tbody></table>

For information about the agent, see
[Setting Up Monitoring for Hybrid Deployments](https://docs.mulesoft.com/monitoring/am-installing).

## June 23, 2026

**Version 3.2.16.3**

The 3.x version of the Anypoint Monitoring agent fixes an issue.

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The <code>Failed to scrape Prometheus endpoint</code> message no longer appears in logs for hybrid standalone deployments on Linux.</p></div></div></td><td><div><div><p>W-22798371, W-22508168</p></div></div></td></tr></tbody></table>

For information about the agent, see
[Setting Up Monitoring for Hybrid Deployments](https://docs.mulesoft.com/monitoring/am-installing).

## May 14, 2026

**Version 3.2.16.2**

The 3.x version of the Anypoint Monitoring agent fixes an issue.

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Fixed an issue in Linux environments where strict <code>requiretty</code> policies caused a service restart loop that made <code>sudo</code> commands fail during background execution with root privileges. This update improves process ID (PID) operations and service management under <code>systemd</code>.</p></div></div></td><td><div><div><p>W-22437518, W-22358399</p></div></div></td></tr></tbody></table>

For information about the agent, see
[Setting Up Monitoring for Hybrid Deployments](https://docs.mulesoft.com/monitoring/am-installing).

## May 5, 2026

**Version 3.2.16.0**

The 3.x version of the Anypoint Monitoring agent fixes these issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Fixed a parsing issue where Anypoint Monitoring agent installer 3.x versions failed to recognize legacy Mule 3 default log patterns. The <code>correlationID</code> is now correctly extracted as a structured field.</p></div></div></td><td><div><div><p>W-20202127</p></div></div></td></tr><tr><td><div><div><p>Resolved an issue that broke Monitoring and Usage-Based Pricing (UBP) metrics when CloudHub reserved properties were incorrectly configured in customer applications.</p></div></div></td><td><div><div><p>W-15609934</p></div></div></td></tr></tbody></table>

For information about the agent, see
[Setting Up Monitoring for Hybrid Deployments](https://docs.mulesoft.com/monitoring/am-installing).

## March 5, 2026

**Version 3.2.14.0**

### What’s New

The 3.x version of the Anypoint Monitoring agent introduces:

- Support for configuring the OTel collector’s internal telemetry log level during installation
  using the `-l` parameter. This feature is available on supported Linux and Windows operating
  systems. Accepted values are `info` (default), `debug`, `warn`, `error`, and `off`.

  Example (Linux): `# am/bin/install -l error`

- Support for enabling tracing during installation using the `-g` parameter. This feature is
  available on supported Linux and Windows operating systems. Sets the port for tracing data that
  comes from Mule runtime (see
  [OpenTelemetry Support in Mule Runtime](https://docs.mulesoft.com/mule-runtime/latest/otel-support)). This parameter
  is disabled by default.

  Example (Linux): `# am/bin/install -g 4317`

For information about the agent, see
[Setting Up Monitoring for Hybrid Deployments](https://docs.mulesoft.com/monitoring/am-installing).

## February 10, 2026

**Version 3.2.12.5**

### What’s New

The 3.x version of the Anypoint Monitoring agent introduces:

- Support for multiple installations of the agent to a single Linux host

- Updated service templates to support the new port configuration

This release also includes a security update.

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>To address vulnerabilities reported in version 3.2.12.1, this release updates io.netty libraries to version 4.1.125.</p></div></div></td><td><div><div><p>W-20516811</p></div></div></td></tr></tbody></table>

For guidance, see
[Install Multiple Agents to a Linux Host](https://docs.mulesoft.com/monitoring/am-installing#install-multiple-agents).

## November 6, 2025

**Version 3.2.12.1**

### What’s New

The 3.x version of the Anypoint Monitoring agent introduces these changes:

- `sudo` access is no longer required to install Anypoint Monitoring agent _unless_ you’re
  installing the agent as a service. Installing as a service always requires `sudo` access.

- The telemetry listening port is now configurable from the Anypoint Monitoring agent installer
  through a `-t` parameter. Example: `$ ./install -t 8889` (defaults to port `8888`)

## September 3, 2025

**Version 3.1.1.13**

The 3.x version of the Anypoint Monitoring agent introduces an enhancement.

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>With the new <code>anypoint.platform.config.analytics.endpoint.patterns</code> property, define patterns for your dynamic endpoints, ensuring consistent normalization and clean, actionable analytics data.</p></div></div></td><td><div><div><p>W-15668536</p></div></div></td></tr></tbody></table>

For more information, see
[Normalize API Paths for hybrid deployments](https://docs.mulesoft.com/monitoring/am-installing#normalize-path) and
[Normalize API Paths for CloudHub and CloudHub 2.0 deployments](https://docs.mulesoft.com/monitoring/configure-monitoring-cloudhub#normalize-path).

## August 20, 2025

**Version 3.1.1.12**

The 3.x version of the Anypoint Monitoring agent fixes these issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>To improve the OTel collector’s functionality when running in service mode, Anypoint Monitoring now registers an internal <code>DirectoryWatcher</code> component as a service.</p></div></div></td><td><div><div><p>W-19256238</p></div></div></td></tr><tr><td><div><div><p>Anypoint Monitoring agent now supports encrypted passwords.</p></div></div></td><td><div><div><p>W-19016971</p></div></div></td></tr></tbody></table>

For more information, see
[Setting Up Monitoring for Hybrid Deployments](https://docs.mulesoft.com/monitoring/am-installing).

See also, [Related Documentation](#related-docs).

## July 1, 2025

**Version 3.1.1.10**

The 3.x version of the Anypoint Monitoring agent fixes an issue:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The agent no longer throws this <code>NullPointerException</code> error: <code>Cannot invoke "java.lang.Boolean.booleanValue()" because the return value of "com.mulesoft.dias.mule.agent.MuleAgentConfig.isTrafficInspectionEnabled()" is null."</code></p></div></div></td><td><div><div><p>W-18900814</p></div></div></td></tr></tbody></table>

For more information, see
[Setting Up Monitoring for Hybrid Deployments](https://docs.mulesoft.com/monitoring/am-installing).

See also, [Related Documentation](#related-docs).

## May 16, 2025

**Version 3.1.1.5**

The 3.x version of the Anypoint Monitoring agent now supports Windows Server 2019.

For more information, see
[Setting Up Monitoring for Hybrid Deployments](https://docs.mulesoft.com/monitoring/am-installing).

See also, [Related Documentation](#related-docs).

## April 1, 2025

**Version 3.1.1.0**

The 3.x version Anypoint Monitoring agent is now available for supported operating systems.

To enhance performance, security, and usability, the agent supports HTTP/HTTPS (instead of SOCKS5)
and the OpenTelemetry (OTEL) standard (instead of Filebeat).

Supported operating systems:

- RedHat Enterprise Linux 9

- Ubuntu 20.04

Windows isn’t supported at this time.

Anypoint Platform Private Cloud Edition (Anypoint Platform PCE) and MuleSoft Government Cloud don’t
support the agent for this version of the installer.

For more information, see
[Setting Up Monitoring for Hybrid Deployments](https://docs.mulesoft.com/monitoring/am-installing).

See also, [Related Documentation](#related-docs).

## September 19, 2023

**Version 2.5.11.2**

## Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The log4j version is updated.</p></div></div></td><td><div><div><p>W-14089178</p></div></div></td></tr></tbody></table>

See also, [Related Documentation](#related-docs).

## Earlier Versions

### June 13, 2022

**Version 2.5.11.1**

## Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The Anypoint Monitoring agent now supports FIPS installation.</p></div></div></td><td><div><div><p>W-10973459</p></div></div></td></tr></tbody></table>

### February 1, 2022

**Version 2.5.11.0**

## Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Custom and inbound metrics stop updating after app redeployment to on-premises 3.9.x.</p></div></div></td><td><div><div><p>SE-23396</p></div></div></td></tr></tbody></table>

### Version 2.5.10.0 October 27, 2021

#### What’s New

- You can now disable application log forwarding.

### Version 2.5.4.0 June 1, 2021

#### Fixed Issues

- Fixed install script issues when two options are passed together, such as SOCKS proxy and skip
  agent installation. (SE-19554)

- Fixed an issue in which inbound metrics did not appear in Anypoint Monitoring for applications
  deployed in a cluster. (SE-20977)

### Version 2.4.2.0 November 19, 2020

#### Enhancement

Anypoint Monitoring now supports PCE 3.0.

#### Fixed Issues

- In the Anypoint Monitoring **Inbound Dashboards** page, the Response Time by Endpoint chart showed
  X instead of the resource URI. (SE-17307)

- App logs were not sent to Log Search when the app was using an incompatible version of the
  commons-lang3 library. (SE-18329)

- You could not install Anypoint Monitoring on hot-fix runtimes.

- The enhanced API metrics were not sent to Anypoint Monitoring.

### Version 2.3.0.0 July 20, 2020

This release contains the following fixed issues:

- Fixed an issue in which metrics were not recorded for a period of time after restarting app on UI
  in Server Group. (SE-16753)

- Fixed an issue in which `filebeat.exe` locked log files, which prevented log files from being
  rotated. (SE-16160)

- Added support for `RollingRandomAccessFileAppender` for Log4j. (SE-16003)

- Fixed an issue in which the **Application Process CPU Load** graph displayed incorrect values.
  (SE-15911)

### Version 2.2.3.0 April 27, 2020

This release contains the following fixed issues:

- Added support for Anypoint Visualizer properties configured from Runtime Manager Properties tab
  for Mule 4. (SE-14999)

- Fixed the issue of not picking the modification for property values unless Mule Runtime is
  restarted. (SE-15543)

### Version 2.2.2.0 April 6, 2020

This release includes the following update:

Header injection for Anypoint Visualizer is enabled by default for Mule 4.

This release contains the following fixed issues:

- Fixed a download connection error when the server is behind a proxy. (SE-15234)

- Fixed an error about am module directory not found. (SE-15374)

### Version 2.2.1.0 February 10, 2020

This release contains the following fixed issues:

- On Mule 4.x, JMX Publisher stopped creating JVM metrics after running for some time. (SE-14730)

  - This fix requires Runtime Manager agent 2.4.5+.

- Outbound metrics erroneously included some internal calls. (SE-14055)

- Some outbound metrics showed an incorrect response time of 24 hours. (SE-13973)

- Improved endpoint normalization. (SE-12965)

- Fixed error on deleting file after copy. (SE-14578)

### Version 2.2.0.0 December 19, 2019

This release contains the following fixed issues:

- Metric logs stopped updating JVM and OS metrics on deployment failure. (SE-13917)

- The Anypoint Monitoring agent was blocking threads. (SE-14121)

### Version 2.1.7.0 August 28, 2019

This release contains the following fixed issues:

- Anypoint Visualizer is not showing inbound connections. (SE-12476)

- Anypoint Monitoring `am` folder is recreated after uninstall. (SE-12769)

- Inbound Metrics are missing for app in Anypoint Monitoring. (SE-12832)

### Version 2.1.6.0 August 6, 2019

This release contains the following fixed issues:

- Log forwarding does not work for newly deployed app without Mule runtime restart. (SE-12605)

- Uninstall script not removing files properly. (SE-12599)

- No infrastructure metrics for certain applications. (SE-12473)

- Analytics collector doesn’t allow to access message. (SE-12446)

### Version 2.1.5.0 July 15, 2019

This release includes the following update:

- Install script no longer requires `-s <server-id>` parameter.

This release contains the following fixed issue:

- Log forwarding does not work with Anypoint Monitoring agent 2.1.4.0 in hybrid runtime. (SE-12410)

### Version 2.1.4.0 June 7, 2019

This release contains the following fixed issue:

- High thread count in a clustered environment (SE-11772)

### Version 2.1.2.0 May 17, 2019

This release includes the following updates:

- Added support for Mule 4.2.x and Runtime Manager agent 2.3.x.

- Added support for Filebeat restart if configuration or certificates have changed.

This release includes the following fixed issues:

- Anypoint Monitoring with Multicast Cluster Setup (SE-11657)

- Layer when deploying app from RM (SE-10374)

- Fix NPE reported in Mule log at startup (SE-11483)

- Some inbound request failures are not taken into account in Monitoring dashboards. (SE-10544)

### Version 2.1.0.0 March 26, 2019

This release includes support for the SOCKS5 proxy. For more information, see
[Install the Anypoint Monitoring Agent](https://docs.mulesoft.com/monitoring/am-installing).

You can download the Anypoint Monitoring agent installer from
[Anypoint Monitoring Agent Installer 2.1.0.0](https://s3.amazonaws.com/cdn-anypoint-prod/artifacts/monitoring-center-ui/app/hybrid/am-2.1.0.0.zip)
or from the Anypoint Monitoring **Settings > Hybrid** page.

### Version 2.0.5.0 February 13, 2019

This release includes the following updates:

- Added metrics for operating system

- Added support for the following versions of Mule Runtime Manager agent:

  - 1.11.x

  - 1.12.x

  - 2.2.x

You can download the Anypoint Monitoring agent installer from
[Anypoint Monitoring Agent Installer 2.0.5.0](https://s3.amazonaws.com/cdn-anypoint-prod/artifacts/monitoring-center-ui/app/hybrid/am-2.0.5.0.zip)

### Version 2.0.4.0 February 11, 2019

This release includes the following updates:

- Added support for Mule Runtime Manager agent version 2.1.8.

- Added support for Mule runtime engine version 4.1.5.

## Related Documentation

In addition to these release notes, see:

- [Anypoint Monitoring Release Notes](https://docs.mulesoft.com/release-notes/monitoring/anypoint-monitoring-release-notes)

- [Update the Monitoring Agent](https://docs.mulesoft.com/monitoring/am-installing#update-the-monitoring-agent.adoc)

- [Anypoint Monitoring](https://docs.mulesoft.com/monitoring/)

## See Also

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