AppDynamics switched from Semantic Versioning to Calendar Versioning starting in February 2020 for some agents and March 2020 for the entire product suite.

    Skip to end of metadata
    Go to start of metadata

    By default, the Machine Agent reports metrics for network-mounted and local disks only. Additionally to ensure backward compatibility with previous versions of AppDynamics, only the external network traffic is aggregated.

    You can customize the default behavior by modifying the auto-generated configuration file, task-template.xml. The task-template.xml file provides information about the current configuration of the Machine Agent and is created when you first start up the agent. It discovers the disks and network hardware on the machine where it is installed that the agent can monitor.

    This configuration applies to the JavaHardwareMonitor extension only. The ServerMonitoring extension is recommended if you have a Server Visibility license and the monitored system meets the system requirements. See Server Visibility Requirements and Supported Environments

    Customize the Default Machine Agent Metric Collection

    1. Locate the task-template.xml file. 
      This file is located in the <machine_agent_home>/monitors/JavaHardwareMonitor/ directory when the Machine Agent starts the first time.
    2. Edit the task-template.xml file:

      • To enable aggregation operation for localhost (lo) network metrics, change the value of the aggregate attribute (for the network element "lo") to "true".
      • To enable monitoring for a virtual disk, set the value of the enabled attribute to "true" for that disk.

      The following is a sample task-template.xml file:

          <disk aggregate="false" enabled="false">sunrpc</disk>
          <disk aggregate="true" enabled="true">/dev/sdb1</disk>
          <disk aggregate="false" enabled="false">proc</disk>
          <disk aggregate="false" enabled="false">none</disk>
          <disk aggregate="false" enabled="false">devpts</disk>
          <disk aggregate="true" enabled="true">/dev/sda1</disk>
          <disk aggregate="false" enabled="false">nfsd</disk>
          <disk aggregate="true" enabled="true">/dev/mapper/saas4-binlog</disk>
          <disk aggregate="false" enabled="false">sysfs</disk>
          <disk aggregate="false" enabled="false">tmpfs</disk>
          <network aggregate="true" enabled="true">lo</network>
          <network aggregate="true" enabled="false">sit0</network>
          <network aggregate="true" enabled="true">eth0:1</network>
          <network aggregate="true" enabled="true">eth0</network>
          <network aggregate="true" enabled="false">eth1</network>
    3. To prevent the Machine Agent from overwriting the file, rename the task-template.xml file to task.xml . 

    4. To monitor a special device that is not enabled, add a file named task.xml in the <machine_agent_home>/monitors/JavaHardwareMonitor/ directory.
      The format of the task.xml file must be exactly the same format as the task-template.xml file. 
      Not all disks and networks must be included in the task.xml file.  If the Machine Agent finds a disk or a network that is not in the task.xml file, then it applies the default properties.

    5. Restart the Machine Agent.

    • No labels