Discussion Feed

Hi J,   Vendoring AppD would be a little problematic, as our binary dependencies would match the system on which you vendor them. For example, if you were to vendor on a Windows or macOS development machine, and then deploy to Linux, that would not work.   Usually it works best to put the appdynamics package in your package.json, and not vendor it. We're of course happy to work through any concerns you have.   Regards, Kyle ... View more

Hi Archana,   This is definitely possible, but we would need to know more about all the specific processes involved.   Regards, Kyle ... View more

Hi Santosh,   Where did you run npm install? Was it the same system which runs the app?   Regards, Kyle ... View more

Hi Adam,   Yikes, Microsoft does like to make our lives difficult... I definitely feel you that having AppD in your normal deployment workflow would be easiest, but unfortunately a re-architecture of our install process is probably not in the cards. It is definitely something we periodically review though—it's possible that as more and more people have end-to-end package-lock deployment workflows we'll opt to take the work on.   But for us in the mean time it means we need to keep hunting for a better process. If global install on the Azure instances isn't possible, and we have to install into the wwwroot, I wonder, could we use a post-deploy script to install the agent? That way you could have a script that basically changes to the wwwroot directory and runs npm install appdynamics@4.5.0. This same script could set the environment variable. (https://github.com/projectkudu/kudu/wiki/Post-Deployment-Action-Hooks)   Another option would be to do this one-off install at build/deploy time in your CI/CD pipeline somewhere, but depending on your environment that may take more effort. In any case, happy to keep working with you to find something that fits your needs!   Regards, Kyle ... View more

No problem! Don't hesitate to reach out again in case you need anything. ... View more

Well, so our central server (what we call the controller), typically offers backwards compatibility for agents. Meaning a 4.4.x controller will support any 4.4.x and previous agents. Also! With 4.5 we're relaxing the forward compatibility restriction. 4.5+ agents will now work with any 4.4.x controllers. I would expect this going foward as well.   Long story short, if you're already on a 4.4 controller, you can and should just use the latest Node.js package. ... View more