cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Why does AppDynamics NodeJS client install Java Runtime Environment within its npm packages?

lukasz
New Poster

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?

3 REPLIES 3

Raunak.Mohanty
AppDynamics Team (Retired)

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

https://docs.appdynamics.com/display/PRO43/Dynamic+Language+Agent+Proxy#DynamicLanguageAgentProxy-No...

 

Let us know if you have additional questions.

 

Thanks,

Raunak



Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.

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? 

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