In an elastic environment where virtual machines are frequently provisioned and terminated, the Performance Analyst should enable node-name reuse by using -Dappdynamics.agent.reuse.nodeName together with -Dappdynamics.agent.reuse.nodeName.prefix.
The reuse setting allows an Application Agent to register against an available historical node identity rather than continually creating a new node record each time a replacement virtual machine starts. The prefix groups reusable node names for a particular tier, service, or deployment pool, ensuring that agents select node identities from the correct logical set. This prevents excessive node proliferation in the Controller and preserves cleaner historical monitoring for short-lived infrastructure.
A typical configuration enables reuse and supplies a stable prefix, for example:
-Dappdynamics.agent.reuse.nodeName=true
-Dappdynamics.agent.reuse.nodeName.prefix=checkout-node
Proxy properties only control Controller connectivity through an HTTP proxy. Node metadata and a fixed node name do not provide controlled reuse across an automatically scaling pool.
Relevant CAAPA Study Guide topics include Dynamic and Elastic Environments, Node Name Reuse, Application Agent Registration, Tier and Node Configuration, and Controller Node Management.