WARNING: Version 6.2 of Metricbeat has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
This functionality is in beta and is subject to change. The design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features.
PHP-FPM server status metrics collected from PHP-FPM.
php_fpm contains the metrics that were obtained from PHP-FPM status page call.
pool contains the metrics that were obtained from the PHP-FPM process pool.
The name of the pool.
Static, dynamic or ondemand.
Connection state specific statistics.
The number of incoming requests that the PHP-FPM server has accepted; when a connection is accepted it is removed from the listen queue.
The current number of connections that have been initiated, but not yet accepted. If this value is non-zero it typically means that all the available server processes are currently busy, and there are no processes available to serve the next request. Raising
pm.max_children (provided the server can handle it) should help keep this number low. This property follows from the fact that PHP-FPM listens via a socket (TCP or file based), and thus inherits some of the characteristics of sockets.
The maximum number of requests in the queue of pending connections since FPM has started.
The size of the socket queue of pending connections.
Process state specific statistics.
The number of servers in the
waiting to process state (i.e. not currently serving a page). This value should fall between the
pm.max_spare_servers values when the process manager is
The number of servers current processing a page - the minimum is
1 (so even on a fully idle server, the result will be not read
The number of idle + active processes.
The maximum number of active processes since FPM has started.
Number of times, the process limit has been reached, when pm tries to start more children (works only for pm dynamic and ondemand).
The number of times a request execution time has exceeded
Number of seconds since FPM has started.
The date and time FPM has started.