Install Agents

You can install agents on a machine by using the UI only if Smart Agent is installed on the same machine.

Note: If installing Machine Agent with Smart Agent on SELinux, configure SELinux to permissive mode. See SELinux Installation Issues.

If you require to use smartagentctl to install Machine Agent or require to install Machine Agent on a remote host, see Install Machine Agent Using smartagentctl.

To install the the supported agents from the Agent Management UI, perform the following steps:

  1. Click Home > Agent Management > Manage Agents.
  2. Click Install Agent in the right pane.
    Note: To ensure that the host is auto-selected on the Install Agent page, select the required single or multiple hosts from the Smart Agents tab, then click Install Agent.
  3. Select the type of agent and then click Next.
  4. Select one of the following to specify the location for deploying the agent, then click Next.
    • Select from List: You can select the host on which Smart Agent is installed from the list, then click the left arrow to list it under selected table. You can select multiple hosts. You can add multiple agents for a single host and multiple hosts can be selected by repeating this step. The Install directory field gets auto-populated based on the host operating system.
      Note: For .Net Agents, only the Windows Smart Agents are available to select.
      The following is an example image of the agent installation page. This screen may change based on the selected agent. Machine Agent does not include the Application, Tier, and Node fields.
    • Import from CSV file: You can upload a CSV file with required columns such as HostName, SmartAgentID, Application, Tier, Node, and Installation Directory.
    Note: If you are installing Java Agent, you can specify the environment variables such as env.Host and env.USER for values under Application, Tier, and Node. For example, if you want the application name to be TomcatApp with the hostname as prefix, edit the application name under Application as {env.HOST}-TomcatApp.
  5. Select Custom Prefix if you want a prefix to be added to the application, node and tier names, else proceed with specifying the application details.
  6. (For Java Agent) To use a single Java Agent to instrument more than one Java process on a machine, you can use a templated node name such as mynode_${appd_auto_name}.
    Every instrumented process will receive a unique resolved node name.
  7. Configure the agent attributes on the Set Agent Attributes page, then click Install.
    1. You can select the download source.
      The source can be the Splunk AppDynamics download portal (Using Cisco AppDynamics Portal), your local directory (Using Local Directory), or your custom HTTP server (Custom HTTP URL).If you selectCustom HTTP URLand if your HTTP server requires authentication, configure smart agent to use basic authentication. See Configure Basic Authentication for Custom Artifactory Location.
    2. You can select Additional Configuration to add more configuration details.
      Use the agent specific custom configurations to specify in Custom Configuration. For the list of keys that you can use, see Custom Configuration. You can add multiple attributes in separate lines.
      Note: Machine Agent: Ensure that you have specified the required custom configuration for the agent and Controller communication. To configure the agent endpoint, add the following to the additional configuration field: 
      analytics_event_endpoint: "https://<IP address or DNS name>:443"
      If you do not specify the endpoint, Smart Agent considers the default value, analytics_event_endpoint: "https://fra-ana-api.saas.appdynamics.com:443". .NET MSI: You can configure only Custom AD_Setup file content. See Additional Configuration for .NET MSI. Also, Install Version is a required field when you select Custom HTTP URL or Using Local Directory. You can specify the use_sa_info: true additional configuration, if you require the agents to use only the Smart Agent connection configuration. This overwrites the same connection configuration from the Controller.
  8. Check the install status in Tasks in Progress.
    You can search for the specific host and check the log file. After the task is completed the task is added to the History tab.
    Note: The log file is generated after the task is complete.