Machine Agent Notes

Related pages:

The following notes describe 4.5.x and 20.3.x updates to the Machine Agent.

If an artifact has been updated, the version number of the updated artifact and its availability date are listed below. The version number corresponds to that shown on the download portal (http://download.appdynamics.com).

The most recent releases appear at the top of the page.

4.5.18 (Agent) Updates

Version 4.5.18.2430 – January 23, 2020

Enhancements

The Analytics Agent bundled with the Machine Agent has been upgraded. See Application Analytics Notes.

Resolved Issues

Key	Summary
SERVER‑6216	The default max heap size for the Machine Agent process is set to 256 MB

4.5.17 (Agent) Updates

Version 4.5.17.2418 – January 6, 2020

Enhancements

The Network Agent bundled with the Machine Agent has been upgraded. See Network Agent Notes.
The Machine Agent now supports Windows 2019.
For Windows, the data source for a subset of metrics is now Operating System and Hardware Information (OSHI) metrics and no longer Windows Management Instrumentation (WMI) metrics. The following metrics have been affected:
- Process Metrics
- CPU
- Memory
See Hardware Resources Metrics for more information.

4.5.16 (Agent) Updates

Version 4.5.16.2341 – October 24, 2019

Enhancements

Server Visibility now supports AIX 7.x. See Hardware Resources Metrics for details of the server metrics reported for this OS. Note, If this version of the agent is used with Controllers older than 4.5.16, there will be an “OS not supported” error message displayed: this can safely be ignored, and will not appear with 4.5.16 or later Controllers.
Support for the Network Visibility Extension in the Machine Agent for Windows.

Resolved Issues

Key	Summary
SERVER‑7129	Upgraded Apache Ant library to 1.10.7

4.5.15 (Agent) Updates

Version 4.5.15.2316 – September 30, 2019

Enhancements

Support for JRE 1.8.0_212 is bundled with the Machine Agent on Solaris and Windows.

Resolved Issues

Key	Summary
SERVER‑7120	Upgraded to Apache Commons BeanUtils 1.9.4

4.5.14 (Agent) Updates

Version 4.5.14.2293 – August 23, 2019

Resolved Issues

Key	Summary
SERVER‑6203	The Machine Agent with HTTP Listener is now using the correct Machine Agent log when the HTTP Listener throws an exception
SERVER-5569	When a Machine Agent uses a proxy, AWS custom tags collection works as expected

4.5.13 (Agent) Updates

Version 4.5.13.2238 – July 24, 2019

Enhancements

A warning appears in the Machine Agent logs if the Machine Agent, and a monitored container, have the same host id.

Resolved Issues

Key	Summary
SERVER‑6348	Install Linux RPM as the root user on RHEL 6

4.5.12 (Agent) Updates

Version 4.5.12.2205 – June 27, 2019

Resolved Issues

Key	Summary
SERVER‑6266	Users no longer see non-APM containers if the controller flag `sim.docker.monitorAPMContainersOnly` is set to true

4.5.11 (Agent) Updates

Version 4.5.11.2163 – May 17, 2019

Enhancements

Support for JRE 1.8.0_212 is bundled with the Machine Agent on Linux.

Resolved Issues

Key	Summary
SERVER‑6344	Enable and Disable Machine Agents is now working as expected

4.5.10 (Agent) Updates

Version 4.5.10.2131 – April 20, 2019

Resolved Issues

Key	Summary
SERVER‑5549	The Machine Agent does not send authorization headers for some REST endpoints

Known Issues

AppDynamics enables the monitoring of all containers on the host machine through the sim.docker.monitorAPMContainersOnly property. This property was formerly named sim.docker.infraMode.enabled. By default, only containers with APM agents running inside are monitored but this behavior can be changed by setting this property to false. There can be a short delay before non-APM containers are monitored when upgrading to the 4.5.10 Machine Agent. This happens when the user sets the sim.docker.monitorAPMContainersOnly property to enable monitoring of non-APM containers but also has sim.docker.infraMode.enabled set to true. In this case, the property name change does not happen immediately and non-APM containers won't be monitored until on-line schema migration happens. This takes approximately 4.5 hours after the Controller starts up.

4.5.9 (Agent) Updates

Version 4.5.9.2096 – March 21, 2019

Resolved Issues

Key	Summary	Affects
SERVER‑4910	The AppDyamics Agents > Machine Agent page is not showing applications associated with each app-agent container	Machine Agent

4.5.8 (Agent) Updates

Version 4.5.8.2073 – February 22, 2019

Enhancements

Support for JRE 1.8.0_162 is bundled with the Machine Agent on Linux.

Resolved Issues

Key	Summary
SERVER‑5685	From 4.5.4 and later, the Machine Agent is missing the secure credential store utility
SERVER-5818	The CPU Busy percentage on Windows is now consistent with the value reported on the Perfmon tool

4.5.7 (Agent) Updates

Version 4.5.7.1975 – January 25 2019

Resolved Issues

Key	Summary
SERVER-5833	Machine Agent version 4.5.2+ fails to start because of com.google.inject.CreationException error

4.5.4 Updates

Version 4.5.4.1735 – October 25, 2018

Resolved Issues

Key	Summary
SERVER‑4577	Cannot update RPM Standalone Machine Agent due to a packaging error

4.5.2 Updates

Version 4.5.2.1611 – October 8, 2018

Enhancements

Starting in 4.5.2, the Machine Agent is backward compatible with Controller versions 4.4.0 and newer.

Resolved Issues

Key	Description
SERVER‑4467	Machine Agent not collecting data when the collector script contains non-ASCII characters
SERVER-4720	The HardwareMonitor extension (OS Specific) reports incorrect memory metrics on RHEL 7.x when REPORT_MEMORY_FREE_AS_MEMORY_AVAILABLE is enabled
SERVER-4892	Machine agent should retrieve agent truststore from the <machine_agent_home>/conf directory, not the <machine_agent_home> directory.

4.5.0 Updates

July 11, 2018

Important Note about Changes in Dynamic Monitoring from Previous Releases

Starting in release 4.5, Dynamic Monitoring Mode (DMM) is enabled by default on all Standalone Machine Agents. Because the default mode for all agents is KPI, only KPI metrics are collected by default in this release. This is true for the following metrics:

Hardware Resources Metrics

This change can affect any user-defined features created in previous releases that rely on Diagnostic or Advanced Diagnostic metrics. Examples include Health Rules, Dashboards, and scripts with metric API calls.

AppDynamics strongly recommends that you disable these user-defined features, edit them to use KPI metrics instead, or increase the Dynamic Monitoring Mode on the relevant agents.

For more information, see

Enhancements

The Standalone Machine Agent is now supported on Windows Server 2016.
The Standalone Machine Agent is no longer supported on Windows Server 2008 or Debian 7.

Resolved Issues

Key	Summary
SERVER‑2081	Machine Agent cannot collect OS info on Red Hat Extended Linux 7.4
SERVER-2417	Enabling sim.machines.reuse.enabled sometimes results in thread pool saturation and prevents Standalone Machine Agent from communicating with Controller
SERVER-2582	In some cases, Machine Agent stops collecting process metrics even after machine/global max thresholds are increased
SERVER-2605	Machine Agent is not reporting processes, networks, and volumes when running in Container
SERVER-4361	Machine Agent not reporting metrics on docker when process command contains space
SERVER-4369	Hierarchy name check is case-sensitive, which prevents Standalone Machine Agent registration
SERVER-4403	Number of CPUs reported by Standalone Machine Agent is sometimes inaccurate on Windows
SERVER-4577	Cannot update RPM Standalone Machine Agent due to a packaging error

Known Issues

Reset Machine Agent action on the AppDynamics Agents window is not available for 4.4 and higher Machine Agents.
(Windows only) The JavaHardwareMonitor extension and the ServerMonitoring extension (introduced in 4.2) assign network names differently. If you have any health rules based on JavaHardwareMonitor names, and you want to use these rules with the ServerMonitoring extension, you will need to update the names that these rules are based on.