Dynatrace Ruxit is proud to announce general availability of PHP deep monitoring. New customers receive PHP support automatically when they install Dynatrace Ruxit.
For existing customers, to enable PHP monitoring:
- Upgrade to Dynatrace Ruxit Agent v1.89 or higher.
- Go to Settings > Monitoring > Monitoring Technologies.
- On the Dynatrace Ruxit supported technologies tab, set the PHP monitoring switch to On.
What you get with PHP deep monitoring
Following restart of the Apache web server that runs PHP, select a web request service for analysis. Once the service receives a PHP request you’ll see a small PHP logo appear next to the Apache logo. Depending on what your PHP code does, once PHP monitoring is successfully enabled you may notice that your Apache web request service now calls Databases and/or other services that are called from within PHP.
Now select a PHP request from the Top web requests list. On the following page, click the View response time hotspots button.
PHP response time analysis and code-level visibility
Notice that you get database requests now—every single SQL statement executed from within PHP is available, just as it is with Java, .NET, and Node.js. If your PHP code makes HTTP requests to other systems, you’ll see those as well.
Click any statement to view more details.
Dynatrace Ruxit currently supports the following databases in PHP:
- MySQL/MariaDB (via mySQL and mySQLi drivers)
- All databases from PDO drivers (see http://php.net/manual/en/pdo.drivers.php)
In the Average response time infographic, click Self time to view the breakdown of your request’s code-level timings. Notice that PHP execution is now a clickable link you can use to view method-level hotspots in your PHP code.
If you’re only interested in why your service consumes a lot of CPU, and not in the response time, you can analyze CPU consumption directly.
PHP compilation times
Dynatrace Ruxit also shows you if your PHP requests spend too much time in compilation.
PHP error analysis
If any of your PHP requests has an increased failure rate you can analyse it by clicking the View details of failures button underneath the failure rate chart.
- The return code of each failed request is displayed. A No response message is displayed if an error broke PHP execution completely. In the example below, you can see that all requests failed because of a
exitfunction in the PHP code.
- Click Details to view the message and access code-level view.
exit function doesn’t include a message, the
exit code is displayed instead.
What about FPM and Nginx?
Dynatrace Ruxit automatically injects into FPM and fully supports Nginx/FPM and any other FPM setup. Dynatrace Ruxit automatically tracks all calls from your Nginx to the specific FPM pool.
Each FPM pool is its own service. In the example below, the pool named www hosts a Magento store. As you can see, Dynatrace Ruxit automatically discovers all requests and identifies the most CPU-intensive and slowest requests
On Linux, Dynatrace Ruxit supports PHP 5.3 and above. Dynatrace Ruxit supports FPM in combination with any WebServer and of course mod_php in the Apache web server.