get_node_extrainfo.sh recipe doesn't return any data when using LEVEL '0'
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start with recipes/get_node_extrainfo.sh and reproduce the empty output using the documented -E and -L options, comparing it with the working -A 4087 invocation. Trace how LEVEL 0 is handled and verify that the recipe returns node data at controller level while preserving the existing CSV output format.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- Shell
- Stars
- 46
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Appdynamics/api-commandline-tool
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
Appdynamics/api-commandline-tool#37 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in Appdynamics/api-commandline-tool
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
AppImage/appimage.github.io#9676 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
YunoHost-Apps/pixelfed_ynh#346 ·
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 2 days
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
ChrisTitusTech/dwm-titus#367 ·
Maintainers usually reply within 1 day