get_node_extrainfo.sh recipe doesn't return any data when using LEVEL '0'

Hi @QuaCKeReD

Thanks for developing the script to extract detailed Node info. However, we've been trying to get the nodes info at controller level and running into issues, as it returns an empty data set.

https://github.com/Appdynamics/api-commandline-tool/blob/master/recipes/get_node_extrainfo.sh

`./get_node_extrainfo.sh -E saas-nonprod -L 1
ENVIRONMENT: saas-nonprod | LEVEL: 1 | APP_ID: | SOURCE: 0 | DEST: 0
appId,appName,nodeId,nodeName,tierName,machineName,machineOSType,machineAgentVersion,appAgentVersion,agentType,jvmVersion,appServerRestartDate`

Running the command with application Id returns expected data

`./get_node_extrainfo.sh -E saas-prod -A 4087
ENVIRONMENT: saas-prod | LEVEL: 0 | APP_ID: 4087 | SOURCE: 0 | DEST: 0
appId,appName,nodeId,nodeName,tierName,machineName,machineOSType,machineAgentVersion,appAgentVersion,agentType,jvmVersion,appServerRestartDate
4087,**-***,800829,10.10.119.11,JMS,***-***-***,Windows,false,Server Agent #20.10.0.31173 v20.10.0 GA compatible with 4.4.1.0 r29ff7e90931b7171bbfd8336067028701025517a release/20.10.0,APP_AGENT,"Java HotSpot(TM) 64-Bit Server VM 1.7.0_71 Oracle Corporation",1638685355644`

Masked some information for security purposes in the above output.

Commencez par recipes/get_node_extrainfo.sh et reproduisez la sortie vide en utilisant les options documentées -E et -L, en la comparant à l’invocation fonctionnelle -A 4087. Suivez la manière dont LEVEL 0 est géré et vérifiez que la recette renvoie les données du nœud au niveau du contrôleur tout en conservant le format de sortie CSV existant.

Rédigé par le modèle d'indexation à partir du texte de l'issue.