Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.
AppDynamics customers and established members should click the sign in button to authenticate.
in our environment the build machines have access to a custom npm registry (based on nexus) that is able to proxy requests to npmjs.org, but otherwise has no internet access. The problem with the NodeJS appdynamics agent is that it tries to fetch dependencies from appdynamics.com.
I published these dependencies (appdynamics-jre, appdynamics-proxy etc.) to our private registry and then tried to publish a "fork" of appdynamics (with its dependencies pointing to that registry), but did not succeed. Is there a general recommendation for this type of scenario?
There are 2 ways for you to install the AppDynamics Node.JS agent in a system with no internet
Way 1 (When you have a system with similar environment with inernet access.)
Install the appdynamics agent in that system in a fresh drive with npm install appdynamics@version. (replace "verison" with the version required)
Copy contents of node_modules folder to the server you want to instrument.
Way 2 (When you don't have a system with same environment)
1: Get the npm user agent by running the command "npm config get user-agent"
2: Use any system with nodejs installed.
3: Backup this system's npm user agent with the same command "npm config get user-agent"
Save the above output to revert the settings back, once we have the appdynamics package.
4: Set the npm user agent in the system with internet to the one we took earlier in step 1 with command 'npm config set user-agent "out put from step 1" '
5: Follow the steps in way 1 on installing the agent & copying the files in node_modules to the target server.
6: Revert the npm user agent by running the command 'npm config set user-agent "out put from step 3" '
Please let us know if you face any issue.
This does not work for me as I need to have a packaged tgz file to upload to nexus3. When it tries to open the packaged file (downloaded from the appdynamics download sites) it fails.
I get this:
root@ip-10-0-0-145:/home/ubuntu/nexus# npm install firstname.lastname@example.org
npm WARN deprecated email@example.com: Use `setimmediate` instead
npm WARN excluding symbolic link node_modules/.bin/n -> ../n/bin/n
npm WARN excluding symbolic link node_modules/.bin/semver -> ../semver/bin/semver
npm WARN excluding symbolic link node_modules/.bin/uuid -> ../uuid/bin/uuid
npm WARN excluding symbolic link node_modules/appdynamics-libagent/node_modules/.bin/sshpk-conv -> ../sshpk/bin/sshpk-conv
npm WARN excluding symbolic link node_modules/appdynamics-libagent/node_modules/.bin/sshpk-sign -> ../sshpk/bin/sshpk-sign
npm WARN excluding symbolic link node_modules/appdynamics-libagent/node_modules/.bin/sshpk-verify -> ../sshpk/bin/sshpk-verify
npm WARN excluding symbolic link node_modules/appdynamics-libagent/node_modules/.bin/uuid -> ../uuid/bin/uuid
npm WARN excluding symbolic link node_modules/appdynamics-libagent-napi/node_modules/.bin/sshpk-conv -> ../sshpk/bin/sshpk-conv
npm WARN excluding symbolic link node_modules/appdynamics-libagent-napi/node_modules/.bin/sshpk-sign -> ../sshpk/bin/sshpk-sign
npm WARN excluding symbolic link node_modules/appdynamics-libagent-napi/node_modules/.bin/sshpk-verify -> ../sshpk/bin/sshpk-verify
npm WARN excluding symbolic link node_modules/appdynamics-libagent-napi/node_modules/.bin/uuid -> ../uuid/bin/uuid
npm WARN excluding symbolic link node_modules/log4js/node_modules/.bin/semver -> ../semver/bin/semver
│ ├─┬ firstname.lastname@example.org
│ │ └── email@example.com
│ ├─┬ firstname.lastname@example.org
│ │ └── email@example.com
│ └── firstname.lastname@example.org
│ ├─┬ email@example.com
│ │ ├── firstname.lastname@example.org
│ │ ├── email@example.com
│ │ ├── firstname.lastname@example.org
│ │ └── email@example.com
│ └── firstname.lastname@example.org
npm WARN enoent ENOENT: no such file or directory, open '/home/ubuntu/nexus/package.json'
npm WARN nexus No description
npm WARN nexus No repository field.
npm WARN nexus No README data
npm WARN nexus No license field.
and nothing in the appdynamics node_modules dir.
Do you have a solution for this?