Have you added the license file to the controller? If so, and it's still not showing the entitlements, you may need to login into the <controller-host>/controller/admin.jsp Admin page, and allocate the licenses. After Login -> Account. Then you can allocate the same licenses in the License Page. Let us know if you have queries. Thanks Ayush ... View more

Hi Devaraj, Please have a look at this link. [Redacted] There are Metrics of GC for each node, and the aggregate GC for all Node.Js in the link above. The screenshot if the GC you showed earlier was from the aggregate one. You can drill down to individual nodes to view the specific GC and other details. Please let us know if you have more queries. Thanks Ayush ^ Post edited by @Ryan.Paredez - Please do not share links to your Controller on the Community for Privacy and Security reasons. If you do need to share this, please do it via a private message within the Community platform.  ... View more

Hi Devraj, Do you see 5 nodes in the Tiers and Node Tab in the application or just one node ? Are you on SAAS, or ON-PREM ? If SAAS, please share the URL when the metric browser is open with this metric. Thanks Ayush ... View more

Hi David, I found this parameters in the Golang documentation which you can use. https://docs.appdynamics.com/display/PRO44/Go+Agent+SDK+Reference Logging – Logging settings for the controller. This struct is defined as: const   (      APPD_LOG_LEVEL_DEFAULT LogLevel = iota      APPD_LOG_LEVEL_TRACE      APPD_LOG_LEVEL_DEBUG      APPD_LOG_LEVEL_INFO      APPD_LOG_LEVEL_WARN      APPD_LOG_LEVEL_ERROR      APPD_LOG_LEVEL_FATAL ) type LoggingConfig struct {      BaseDir             string      MinimumLevel        LogLevel      MaxNumFiles         uint      MaxFileSizeBytes    uint } ... View more

Hi Ahmed, We need some more information about the setup. OS Apache version Mod _PHP or PHP-FPM Please attach the apache configuration for appdynamics after removing the value for controller url & access key. Thanks Ayush ... View more

Hi Ahmed, Here is the information the Apache/WebServer agent collect by default. https://docs.appdynamics.com/display/PRO43/Apache+Web+Server+Agent Thanks Ayush ... View more

Hi Shiva, As we have discussed in earlier tickets, that the Node.JS agent has native dependencies thus when installed it gets the compatible package from our repository. It seems that your Node.JS environment in AWS is different from the one in local. Otherwise the agent download/install should work seamlessly. Could you please confirm the same by checking the npm user agent config from both the local docker & the one running in AWS. Here is the command to check the same. npm config get user-agent Thanks Ayush ... View more

Hi Shiva, Thanks for the update. Glad it worked. Thanks Ayush ... View more

Hi Shiva,  When you start the Node.JS application in debug mode, the log location is logged out in the console. You can get it from there. It should be /tmp/appd for any linux machines. Thanks Ayush ... View more

HI Shiva, Please let us know if you still face issue. Thanks Ayush ... View more

Hi Shiva, Right now Node.JS version 8.x is not supported. It should be out in coming weeks.  Rightnow you can use the agent for any Node.JS version 7.x. Thanks Ayush ... View more

Hi Shivakumar, AppDynamics Node.JS agent has native dependencies, hence, spoofing the user agent to get appdynamics will not suffice the agent installation.  As per your spoofed user agent, ou downloaded the appdynamics package for Node.JS 0.10.41, hence its not working. Since you have a 4.3 controller, could you try installing by using the appdynamics package by the command  npm install appdynamics@4.3 Please revert to the original useragent before installing. Please also make sure to have the appdynamics profile block to be the first line in the script. Thanks Ayush ... View more

Hi, About the two issue you are facing  Segmentation fault (core dumped) Do you have a core dump ? Is OpCache enabled ? If yes, could you try disabling that & check if the same can be reproduced. PHP Warning: Unsupported exit call type (missing delegate) in /srv/www/... Are you getting this continiously throughout the application lifecycle?  While the application is started, there is a delay to get the config from Controller. So this is when you get this error. This should go away when the agent gets the config from the controller. The 2000us wait to get config is between the PHP process & the Proxy. Thus for an IPC this is not too short TTL. Is it possible to share the trace level logs & core dump if any. Then I would share an SFTP credentials for same. Please don't attach them here as it might contain sensitive information. Thanks Ayush ... View more

Hi Sujith, Here is the documentation for PHP agent in MAAS configuration. https://docs.appdynamics.com/display/PRO43/Multiple+PHP+Apps+on+a+Single+Servers It is required to providing a default, app, tier and node name in appdynamics_agent.ini. So that if there is a virtual host/app which doesn't have the app, tier & host name, the php agent will take the default from the appdynamics_agent.ini. Else it would be a invalid config for the PHP agent till you set the values in .htaccess or fpm conf etc. Hope it make things clear. ... View more

Hi Sujith, Here is the download link for the PHP agent 4.2.15.9  https://download.appdynamics.com/download/#version=4.2.15.9&apm=php&os=&platform_admin_os=&events=&eum=&page=1 Thanks ayush ... View more

Hi If your controller version is 4.2.x, you can install any PHP agent 4.2.x. The latest PHP agents compatible with 4.2 controller is 4.2.15.9. We recommend using the latest 4.2 agent. You can download the agent from this URL. (Needs Authentication)  Thanks ... View more

Hi Christian, 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. Thanks Ayush ... View more

Hi, Sorry you had to face the issue. Its a known issue, and we have resolved it, and the fix will out in next release. In the mean while, I would request you to try installing the dependencies, directly using. pip install appdynamics-bindeps-linux-x64 appdynamics-proxysupport-linux-x64 Or is possible use lower version python than 3.4. Thanks Ayush ... View more

Hi,  Could you do a ls -lf in the agent installed directory and send us the output, I belive it will be in your <virtual environment>/lib/pythonX.x/site-packages/. There is a open issue with Python 3.4+, I just want to make sure its not the case. It couldn't find appdynamics, and you also iterated that you are unable to install. What error are you getting while installing. Is it possible to run you application in Python 2.7 ? Thanks Ayush ... View more

Hi, In your node application you initiate the appdynamics profiler like require("appdynamics").profile({ controllerHostName: '<controller host name>', controllerPort: <controller port number>, controllerSslEnabled: false, // Set to true if controllerPort is SSL accountName: '<AppDynamics_account_name>', accountAccessKey: '<AppDynamics_account_key>', //required applicationName: 'your_app_name', tierName: 'choose_a_tier_name', nodeName: 'choose_a_node_name', }); You need to add the  proxyAutolaunchDisabled: true, proxyCtrlDir: '/tmp/appd/proxy_ctrl_dir', to the same block. Please remember to start proxy first, and use the same file location for control and logs directory. Thanks Ayush ... View more

Explaining a bit further. If the process manager spins up only 1 instance, it will work perfectly. As its same as just running application with node app.js. But if you use of PM2 is to run multiple processes/instances, in which case there may be an issue. As with each instance a new proxy could be spinned. Thus we suggest starting the proxy manually, and the steps are as follows Create two directories /tmp/appd/proxy_ctrl_dir & /tmp/appd/logs In Appdynamics config for NodeJS Set proxyCtrlDir as /tmp/appd/proxy_ctrl_dir Set proxyAutolaunchDisabled as true Then start the proxy manually as described in the documentation  nohup /<application_root_dir>/node_modules/appdynamics-proxy/proxy/runProxy -j /<application_root_dir>/node_modules/appdynamics-jre/jre – /tmp/appd/proxy_ctrl_dir /tmp/appd/logs &  https://docs.appdynamics.com/display/PRO42/Run+the+Proxy+Daemon+Manually+for+Node.js+Agents Then start the NodeJs application so that with any number of instance, there is only one proxy. ... View more

Hi, If you want to use a process manager like PM2, you need to start the proxy manually.  AppDynamics NodeJs agent talk to the controller via a proxy, there should be only one instance of proxy running. When you use a process manager like PM2. It may start multiple proxy which creates issue. Here is the documentation to start the proxy manually.  https://docs.appdynamics.com/display/PRO42/Run+the+Proxy+Daemon+Manually+for+Node.js+Agents ... View more

Hi, Windows NodeJS agent is supported only for 64bit architecture. Thanks ... View more