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

    You are viewing an old version of this page. View the current version.

    Compare with Current View Page History

    « Previous Version 103 Next »

    Related pages:

    Your Rating:
    Results:
    1 Star2 Star3 Star4 Star5 Star
    0 rates

    AppDynamics provides flexibility for configuring the Machine Agent so that you can choose the best fit for your deployment environment. 

    Not all options are available for all properties. See Machine Agent Configuration Properties

    Configure the Machine Agent Properties

    You can configure the Machine Agent by:

    • Editing the controller-info.xml file located in the <machine_agent_home>/conf directory.
    • Adding Agent system properties (-D<system_property>) to the Machine Agent start-up script or on the command line.
    • Using environment variables. To configure the Agent with environment variables, set the value of the environment variable in the environment where the monitored application runs and restart the Agent. Environment variables exist for most of the Agent settings in the controller-info.xml file, but not all settings are configurable through environment variables. For those settings, you need to use system properties or controller-info.xml. See Machine Agent Configuration Properties

    Empty spaces and special characters are not allowed in either the full path to the Machine Agent home directory, or in the directory name itself. If the Machine Agent does not start up, review the path to determine if it contains empty spaces or special characters. For example, the path /opt/appdynamics/machine agent is problematic, however, the path/opt/appdynamics/machine-agent works correctly.

    The JVM system properties and environment variables override the settings in the controller-info.xml file. The Agent applies the first non-empty value for a configuration property. The Machine Agent applies configurations using the following sources (in order).  

    1. Environment variables
    2. System properties passed in the start command for the JVM
    3. Global configuration file: <machine-agent-home>/conf/controller-info.xml

    See Where to Specify Machine Agent Configuration for OS environment and install package details

    Example Configuration

    Machine Agent controller-info.xml File

    <?xml version="1.0" encoding="UTF-8"?>
    <controller-info>
    
    	<controller-host>192.10.10.10</controller-host>
    	<controller-port>8090</controller-port>    
        <account-access-key>165e65645-95c1-40e3-9576-6a1424de9625<account-access-key> 
    	<controller-ssl-enabled>false</controller-ssl-enabled>
    	<enable-orchestration>false</enable-orchestration>
        <sim-enabled>false</sim-enabled> 
        <unique-host-id>your-host-id</unique-host-id>   
        <!-- The following account-related parameter is necessary only for SaaS installations-->
    	<!--account-name></account-name-->	
    
    </controller-info> 


     bash command-line example 

    <machine_agent_home>/bin/machine-agent -Dappdynamics.controller.hostName=192.10.10.10 
    -Dappdynamics.controller.port=8090 -Dappdynamics.agent.accountAccessKey=165e65645-95c1-40e3-9576-6a1424de9625 -Dappdynamics.agent.uniqueHostId=your-host-id

    • No labels