Customize Agent Installer

This page explains how to fine-tune the Agent Installer configuration. Changes apply to the Agent Installer Platform configuration file, config.json. 

Customize Agent Installer Platform Configuration

The Agent Installer Platform has several commands available to customize the configuration. You can run the commands during or after installation, and issue the commands to the zfictl executable, located in the Agent Installer Platform directory. The Agent Installer Platform periodically checks the configuration file and applies the changes.

Do not modify the zero-config.json file directly as this may result in undefined behavior.

View Command Flags

To view the available flags for a command, enter: 

<install-directory> bin/zfictl <command> -h

For example, to view the available flags for the install command, enter:

<install-directory> bin/zfictl install -h

The output example displays the flags with the data type for the parameters and descriptions for the install command:

<install-directory> bin/zfictl install -h
...
Install Agent Installer Platform


Usage:
  zfictl install [flags]


Flags:
      --log-level string                 Logging level (choose from [panic fatal error warning info debug trace])
      --max-log-rate int                 Maximum log msg rate (default -2)
      --disable-instrumentors strings    Instrumentors to disable (choose from [java tomcat jboss glassfish weblogic websphere all])
      --enable-instrumentors strings     Instrumentors to enable (choose from [java tomcat jboss glassfish weblogic websphere all])
      --application string               Controller application name
      --account string                   Controller account name
      --access-key string                Account access key
      --service-url string               Service URL
      --javaagent string                 Java agent (choose from [dynamic ibm sun])
      --jboss-log-manager-modify         LogManager args for JBoss (choose from [true false])
      --proxy-url string                 Proxy URL
      --install-path string              Agent Installer Platform installation path (default "/opt/appdynamics/zeroagent")
      --systemd                          Install in systemd (default true)
  -h, --help                             help for install
     

Run Commands with Flags During and After Installation

You can run commands in the zfictl binary after installation. To make changes during installation, add flags to the installation script.

For example, to configure the log level to info:

During installation (as a flag), enter:

sudo ./zero-agent.sh install --application 'AgentInstallerTestApp' --account 'project-zero' --access-key 'myaccesskey' --service-url 'https://test.saas.appd-test.com' --log-level=info

After installation (using the zfictl executable), enter:

<install-directory> bin/zfictl configure --log-level=info

Connect the Agent Installer Platform to a Proxy

The Agent Installer supports connections with unencrypted proxies only. To configure the zfictl executable to use a proxy connection, enter:  

<install-directory> bin/zfictl configure --proxy-url=http://localhost:1001 

Change Tier Names

The Agent Installer automatically creates a name for every instrumented tier. To create names, the installer extracts information from the Java process, such as the application server name. 

Contact AppDynamics Support to change the name of an instrumented tier. Because an AppDynamics Support representative applies the changes, you need to create a new user named appd_rule_user, and then give appd_rule_user Install Agent permission only. This secures your sensitive data.  

When you contact AppDynamics Support, provide the log in credentials for appd_rule_user. 

Override Systemd Integration

If you do not want the Agent Installer to integrate with systemd in a sudo installation, add -systemd false to the install command, see Use the Agent Installer. For example:

sudo ./zero-agent.sh install --application 'AgentInstallerTestApp' --account 'project-zero' --access-key 'myaccesskey' --service-url 'https://test.saas.appd-test.com' --systemd=false

Maintain Continuous Operation with watchdog

The Agent Installer includes a watchdog process to ensure continued operation of these standalone agents and their related processes:

• Agent Installer Platform Daemon
  
• Machine Agent

If you integrate the Agent Installer with systemd, a profile is created for the watchdog process to ensure that it starts after a planned or unplanned reboot of the system. The systemd profile also restarts the watchdog process if it was terminated during regular operation. 

If you do not integrate the Agent Installer with systemd (by setting --systemd=false), you can create a systemd profile after installation.

If you do not have a systemd profile, then you must start the watchdog process manually to ensure operation of the standalone agents and their related processes.

If you enabled the SELinux module on your system, then you must configure it to ensure that the watchdog and other Agent Installer Platform processes are not blocked.

To start the watchdog process, enter: 

<install-directory> bin/zfictl start

To stop the watchdog process, enter: 

<install-directory> bin/zfictl stop

See Agent Installer for more information. 

Start or Stop Individual Agents 

You can use the watchdog process to start and stop individual agents (Machine or Zero) on the Agent Installer Platform. You can also view or print the status of the managed agents. 

For example, to start the Machine Agent, enter: 

<install-directory> bin/zfictl start machine
Starting Machine Agent 
...
Machine Agent started successfully

For example, to stop the Zero Agent, enter: 

<install-directory> bin/zfictl stop zero
Stopping Zero Agent 
... 
Zero Agent stopped successfully

To view or print the status of the managed agents, enter: 

<install-directory> bin/zfictl status