You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To my knowledge, it's not possible to configure PHP-FPM slow logs to contain the full request URL.
This is a major problem for web applications like WordPress that utilize a front-controller pattern, where every URL maps to a single PHP script, such as wordpress/index.php.
As far as I know, cross-referencing slow log timestamps with access log timestamps is the best workaround, which is tedious and impossible for high-traffic sites, as second granularity can be insufficient, and the subsecond timestamps of the slow log and access log may not match.
The text was updated successfully, but these errors were encountered:
Description
To my knowledge, it's not possible to configure PHP-FPM slow logs to contain the full request URL.
This is a major problem for web applications like WordPress that utilize a front-controller pattern, where every URL maps to a single PHP script, such as
wordpress/index.php
.As far as I know, cross-referencing slow log timestamps with access log timestamps is the best workaround, which is tedious and impossible for high-traffic sites, as second granularity can be insufficient, and the subsecond timestamps of the slow log and access log may not match.
The text was updated successfully, but these errors were encountered: