I frequently make use of the "top" command to determine what's trying out assets. Mostly it pops up having a lengthy listing of Apache httpd processes, that is not so helpful. Can there be in whatever way to determine an identical list, but so that I saw which PHP scripts etc. individuals httpd processes are really running?

If you are worried about lengthy running processes (i.e. demands that take greater than a second or two to complete), you'll have the ability to get a concept of them using Apache's mod_status. Begin to see the documentation, as well as an example of the output (from www.apache.org). This is not unique to PHP, but is applicable to anything running in a apache process.

Observe that the www.apache.org status output is openly available most probably for demonstration reasons -- you would restrict use of yours to ensure that not everybody can easily see it.

The php scripts happen so quick, top wouldn't demonstrate greatly. Or it might zip by quite rapidly. Most webrequests are very quick.

I believe your best choice is always to have some form of real-time log processor, that stored track of your access logs and updates stats for you personally of average run time, memory usage and things like that.

Make your PHP pages time themselves and write their path and execution time for you to file or database. Observe that would slow everything lower when you were monitoring, however it would function as a good calculating method.

It can't be that interactive though. You'd have the ability to get daily or weekly is a result of it, but it would be difficult to see something significant in a few minutes or hrs.

There is a top-like ncurses-based utility known as apachetop which supplies realtime log analysis for Apache. Regrettably, the project continues to be abandoned and also the code is affected with some bugs, however it's really greatly functional. Just don't run it as being root, run it as being any user with accessibility web server log files and you ought to be fine.