The Splunk AppDynamics app agent operates substantially the same way in a dynamic environment as it does in a traditional data center. However, these considerations apply when deploying agents in dynamic environments:

• Ensure that the agents can reach your Controller. Particularly if your Controller operates on-premises while the agents run on hosted servers, you need to ensure that the agents can access the Controller through the firewalls in your environment.

• Configure custom node expiration handling. By default, the Controller manages the lifecycle for a node based on default timeout settings. You will likely want to reduce the default expiration times for nodes, as described in Historical and Disconnected Nodes. To manage this directly, rather than relying on activity timeouts, a strategy would be to run a script in the JVM before it shuts down that invokes the mark-nodes-historical resource in the Splunk AppDynamics REST API to declare itself historical to the Controller.

• Depending on the nature of your environment, it may not make sense to track each JVM instance as a distinct node in Splunk AppDynamics, since the set of nodes, in this case, would be boundless. Also, since the JVMs are identical, representing them as different nodes in Splunk AppDynamics does not best reflect the logical model of the environment.