Discussion Feed

kyle.furlong

Hi Emrul, Yeah, the way we do this in Node.js is through the agent API: https://docs.appdynamics.com/display/PRO44/Node.js+Agent+API+Reference. Specifically, there are two options: https://docs.appdynamics.com/display/PRO44/Node.js+Agent+API+Reference#Node.jsAgentAPIReference-txn.addSnapshotData(key,value) https://docs.appdynamics.com/display/PRO44/Node.js+Agent+API+Reference#Node.jsAgentAPIReference-txn.addAnalyticsData(key,value) addSnapshotData will just add a key value pair to each request snapshot that the agent takes, while the addAnalyticsData will work more like a data collector, providing metrics. Please let us know if you have any issues. Regards, Kyle

kyle.furlong · ‎02-21-2018

Hi Gabriel, We host these subdependencies on our own repository so that we can dynamically serve different artifacts based on the npm user-agent. We leverage this capability to target the correct native binaries for your particular Node.js version, platform, and architecture. Since npm provides no facility to do this kind of targetting, we unfortunatley can't use their registry for these dependencies. Is there are particular reason you don't want to use packages.appdynamics.com? Best, Kyle

kyle.furlong · ‎02-20-2018

Hi Gabriel, It's safest to leave them in place for now. We have long terms plans to eliminate the old code at some point, but currently there may be unintended impact to removing them. However, if you're feeling bold and need to space savings, probably you can remove the jre subdependency. Regards, Kyle

kyle.furlong · ‎02-20-2018

Hi Gabriel, The best way to accomplish an offline install is to package up an archive of the package folders, then simply transport them from the node_modules folder on the build machine to the node_modules folder on your app server. There's one tricky bit which is that the npm user-agent on the build machine needs to match the one on your target server. You can ensure this by using this pair of commands: npm config get user-agent npm config set user-agent Please let me know if you have any issues with this workflow. Regards, Kyle

kyle.furlong · ‎02-19-2018

Hi Molinaro, It looks like the agent is started properly, but it hasn't yet seen even one request to the PHP server. Could you drive some load and re-send the logs if the data doesn't show up on the UI within 5 minutes? Regards, Kyle

kyle.furlong · ‎01-25-2018

Hi Deva, Unfortunately an app restart is necessary to pick up any agent settings changes, including logging levels. Regards, Kyle

kyle.furlong · ‎12-06-2017

Hi Gabriel, While we only officially support the Windows OSes specified in the docs, I've run the agent on other Windowses and have had some success. Give it a try and let us know if it works for you. Regards, Kyle

kyle.furlong · ‎12-06-2017

Hi Gabriel, If you're using the proxyless mode you will not have to worry about the proxy on Windows. Regards, Kyle

kyle.furlong · ‎12-05-2017

Hi Gabriel, Very interesting. We'll keep that in mind in the future. Nice detective work. Regards, Kyle

kyle.furlong · ‎12-04-2017

Hi Gabriel, I hate to do this, but I think the only way forward at this point would be to put together a small app that reproduces the issue so that our engineers can take a look at this. Would that be possible? Regards, Kyle

Date Registered	‎06-10-2013 02:27 PM
Date Last Visited	yesterday
Total Messages Posted	84
Total Kudos Received	10

Discussion Feed

Re: How do I instrument .JS agents to report infor...

Re: [NodeJS] AppDynamics sub-dependencies on npm r...

Re: [NodeJS] Ignoring unnecessary agent dependenci...

Re: [NodeJS] Installing AppDynamics agent sub-depe...

Re: PHP agent on AWS not connecting to the control...

Re: How dynamically change the log level in Nodejs...

Re: NodeJS Agent on Windows non-Server version

Re: PROXYLESS NodeJS Agent on Windows Server with ...

Re: Proxyless NodeJS - BTs being named with "FIXME...

Re: Proxyless NodeJS - BTs being named with "FIXME...