Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
08-02-2017 02:49 AM
Why does AppDynamics NodeJS client install Java Runtime Environment within its npm packages? We find this to be an undesired dependency in containerised NodeJs applications. Is there a native nodejs client or plans to develop one?
Solved! Go to Solution.
08-02-2017 03:14 AM
Hi lukasz,
This is explained in following document
https://docs.appdynamics.com/display/PRO43/Dynamic+Language+Agent+Proxy
https://docs.appdynamics.com/display/PRO43/Node.js+Agent#Node.jsAgent-Node.jsAgentandtheJavaProxy
With 4.3, Node.Js Agent supports proxiless option with few limitations
Let us know if you have additional questions.
Thanks,
Raunak
08-04-2017 01:46 AM
I understand I can make the nodejs agent not use the Java proxy (
https://docs.appdynamics.com/display/PRO43/Dynamic+Language+Agent+Proxy#DynamicLanguageAgentProxy-No...), but it will be installed anyway along the npm package? This still adds 160MB to container image. Would it be safe to delete the appdynamics-jre and appdynamics-proxy packages if the proxiless option is in use? Or is there an alternative npm package which does not include JRE and proxy dependencies?
08-04-2017 03:27 AM
Hi lukasz,
Yes, you can delete these two directories after the agent installation if you do not intend to use the JAVA proxy for controller communication. But, be informed that there are a few functionalities which are still not supported by native agent.
Best Regards,
Piyush
User | Count |
---|---|
3 | |
2 | |
1 | |
1 |
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form