Flex Gateway新着情報
Governance新着情報
Monitoring API ManagerThese release notes are for patches made to the Anypoint Monitoring agent installer.
In addition to these release notes, see:
If you update the Runtime Manager agent, you must execute the Anypoint Monitoring agent uninstall script and then re-install the Anypoint Monitoring agent. |
Version 2.5.11.2
Issue Resolution | ID |
---|---|
The log4j version is updated. |
W-14089178 |
Version 2.5.11.1
Issue | ID |
---|---|
The Anypoint Monitoring agent now supports FIPS installation. |
W-10973459 |
Version 2.5.11.0
Issue | ID |
---|---|
Custom and inbound metrics stop updating after app redeployment to on-premises 3.9.x. |
SE-23396 |
You can now disable application log forwarding. For more information, see the help article on disabling Monitoring logs.
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.
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)
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)
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)
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)
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)
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)
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)
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)
This release contains the following fixed issue:
High thread count in a clustered environment (SE-11772)
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)
This release includes support for the SOCKS5 proxy. For more information, see Install the Anypoint Monitoring Agent.
You can download the Anypoint Monitoring agent installer from Anypoint Monitoring Agent Installer 2.1.0.0 or from the Anypoint Monitoring Settings > Hybrid page.
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