Setting of probeNameEnvKey isn't reflected.

Document ID : KB000095024
Last Modified Date : 28/05/2018
Show Technical Document Details
Question:
Set probe-name on probNameEnvKey in config.json in the second way in the manual below. But, the probe agent name was not changed in Investigator. 
Example: 
"probeNameEnvKey": "NODE_APP_ID", 

"Configure APM for Node.js" - "Ways to Configure a Custom Name for the Node.js Probe Agent" 

--Ways to Configure a Custom Name for the Node.js Probe Agent-- 
1.The CA_APM_PROBENAME environment variable 
2.The probNameEnvKey environment key that is specified in the config.json file property. 
3.The Node.js Probe Agent name is set using a require statement in the Node.js application startup script. 
4.Configure the probeName property in the config.json file. 
---- 

Is it necessary to set something other than setting "probeNameEnvKey" in the config.json file? 
Where is the value of probeNameEnvKey used? 
Answer:
The Node.js Probe Agent seeks its name in the following priority order, which corresponds to the configurable agent naming methods. If the agent does not find its name in one step, it automatically goes to the next step. 
1. The CA_APM_PROBENAME environment variable 
2. The probNameEnvKey environment key that is specified in the config.json file property. 
3. The Node.js Probe Agent name is set using a require statement in the Node.js application startup script. 
4. Configure the probeName property in the config.json file. 

For the second probeNameEnvKey, create an environment variable with the value specified for probeNameEnvKey, 
It is necessary to set an arbitrary probe name in the environment variable. 
An example 
"probeNameEnvKey": "NODE_APP_ID", 
export NODE_APP_ID = (probe-name)