Choose an Effective Configuration Strategy
- Use versioned agent properties and versioned configuration files before using global agent properties and global configuration files. This minimizes any impact of configuration format changes in future agent releases.
- The agent only reads versioned agent properties and versioned configuration files from one versioned directory. During upgrades, manually migrate configurations from directories for previous versions. See Upgrade the Java Agent.
- The Agent Download Wizard automatically configures the agent using a versioned
configuration file. The configuration in
controller-info.xmlstatically defines the agent identity. - For dynamic or elastic environments that require flexible agent identity, use an
approach that provides for the dynamic node identification.
For example, pass node identify or other agent configuration settings dynamically using environment variables or system properties.
- For shared binaries among multiple JVM instances, Splunk AppDynamics recommends you use a combination of configuration files and startup properties to
configure the app agent. In this case, you configure properties common to all JVMs
in the
controller-info.xmlfile. Then specify the properties unique to each JVM using environment variables or system properties. See Instrument Multiple JVMs on a Single Machine for example configurations. - For some properties, you can use system properties already defined in the startup script as the Java Agent property values. For more information, see Use System Properties for Java Agent Settings.