Agent Reuse Node Name
Set this environment variable to true to reuse node names in AppDynamics. When you set the property to true, you don't need to supply a node name, but you do need to provide a node name prefix using APPDYNAMICS_AGENT_REUSE_NODE_NAME_PREFIX
.
This property is useful for monitoring environments where there are many CLRs with short life spans. When true, Splunk AppDynamics reuses the node names of historical CLRs for new CLRs. Reusing node names avoids a proliferation of differently named nodes in Splunk AppDynamics over time, particularly when the nodes are essentially identical processes that run over different times.
Splunk AppDynamics generates a node name with App, Tier, and Sequence number. The node names are pooled. For example, the sequence numbers are reused when the nodes are purged (based on the node lifetime).
When the .NET Agent for Linux starts up, it logs output to the console until it registers with the Controller and the Controller generates the node name.
The Controller reuses node names based on the node.retention.period
property. See Historical and Disconnected Nodes.
- Environment Variable:
APPDYNAMICS_AGENT_REUSE_NODE_NAME
- Type: Boolean
- Default: False
- Required: No
- Example: Using the following environmental variable specifications, the Controller generates a node name with the prefix reportGen. Node names will have suffixes --1, --2, and so on, depending on the number of nodes are running in parallel. The name of a node that is shut down and qualifies as a historical node may be reused by a new node. APPDYNAMICS_AGENT_REUSE_NODE_NAME=trueAPPDYNAMICS_AGENT_REUSE_NODE_NAME_PREFIX=reportGen