Discussion Feed

Kyle.Furlong

Hi Sandor, Yes, this is expected with ionCube loader. I don't yet have a timeline for this support.

Kyle.Furlong

Hi Sandor, Unfortunately we don't yet support the ionCube loader module. I suspect these crashes are due to that module being used, as we've experienced in the past.

Kyle.Furlong · ‎01-17-2019

Hi Chris, If the pyagent proxy "watchdog" is looping, likely what's happening is that the Java process is not starting up properly. We want to recursively check the permissions on each of these directories: /tmp/appd, the Python module directory. The user which runs the Python process and the pyagent proxy command should have read execute on both. Let me know if that helps! Regards, Kyle

Kyle.Furlong · ‎01-03-2019

Hi Richard, I think the place to start is to ensure you've got some machine agents deployed on these PHP nodes. Then you can correlate any changes in CPU usage with other data in the AppDynamics dashboard. For example, you could navigate to the Node dashboard for one of the PHP machines, and select the Server tab. Then you could find the high CPU time range in the graphs, and click+drag to zero-in on only that time range. Now every UI will use this time range throughout the product. Then, you can inspect snapshots in the time range to see what might be consuming the CPU. In my experience with PHP, we sometimes see this come up when there's a large resultset coming back from a DB or other backend, and the PHP code is looping over it to do some level of transformation of the data. Perhaps this transformation code was stable and solid while this app was growing, but now that the data is reaching a certain threshold, it's leading to issues. Just one possibility. Let me know if that helps! Regards, Kyle

Kyle.Furlong · ‎10-26-2018

Hi Richard, I believe we can use the ${ENVVAR} substitution syntax in this case. So you could do: php_value agent.nodeName ${HOSTNAME} Assuming that HOSTNAME is in the environment variables for the Apache process.

Kyle.Furlong · ‎10-25-2018

Hi Tim, Could you provide the output of phpinfo() run through the server, as well as the PHP error logs? Regards, Kyle

Kyle.Furlong · ‎10-18-2018

Hi Steve, This message is completely normal. What this is saying is that during the time before we've identified your Symfony transaction, we can't yet send out the information to a downstream agent. This means that these HTTP exit calls will not correlate. If you would like these calls to have correlation, you can disable the PHP MVC transaction detection. In that case you'd have the BT discovered based on URL. Please let us know if you have any further questions or concerns. Regards, Kyle

Kyle.Furlong · ‎10-18-2018

Hi Tim, Usually with nginx, the actual PHP server is php-fpm. You may need to restart this service as well. Could you give that a try and let us know if the data shows up? Regards, Kyle

Kyle.Furlong · ‎09-19-2018

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

Kyle.Furlong · ‎09-11-2018

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

Date Registered	‎06-10-2013 02:27 PM
Date Last Visited	13 hours ago
Total Messages Posted	113
Total Kudos Received	20

Discussion Feed

Re: PHP segfault

Re: PHP segfault

Re: Django apache wsgi config

Re: CPU profiling in PHP

Re: PHP Agent configuration using Linux environemn...

Re: PHP Agent installation

Re: PHP agent: framework detected, but BT is still...

Re: PHP Agent installation

Re: Adding AppDynamics to a nodeJS PCF buildpack

Re: How to instrument UNIX application with Smallt...