PHP-FPM
See whether every PHP-FPM worker is busy, how many requests are queuing for one, and which script each worker is running and for how long, from the pool's status page on this host with read-only requests. This plugin is in the next Secronyx release; the current download does not include it yet.
What it answers
Questions an on-call engineer asks, which an AI client can answer with this plugin.
- Are all PHP-FPM workers busy, and are requests queuing for one?
- Has the pool reached its limit of worker processes?
- Which PHP script is each worker running, and for how long?
- Which workers used the most CPU or memory on their last request?
- When did the PHP-FPM pool last restart?
What it returns
Each of the plugin's read-only tools, described in words.
- The PHP-FPM pool's load in one row - active, idle and total workers, requests waiting in the listen queue and its peak, times pm.max_children was reached, slow requests, accepted connections, uptime
- Every PHP-FPM worker, one row each - state (Idle, Running), the script it runs, how long the request has taken, method, request path without query string, and its last request's CPU and memory
At a glance
- Plugin
- php-fpm 1.0.0
- Publisher
- levantar
- Platforms
- Linux
Tested on
- PHP-FPM 8.2.35 and 8.3.36 behind NGINX 1.30.6 on Linux (Ubuntu 24.04, Docker), test lab
How it logs in
Without an explicit choice, install tries the methods that need no secret first, in this order.
- No login (a local endpoint)
Least privilege
The setup file in the pack. This plugin needs no password and creates no login: the file says what it needs on the host and how to keep that to the minimum.
See it run
Read-only, in layers
Every request is a GET or HEAD to the endpoint the operator configured, on a path fixed in the signed pack. Redirects are not followed, and requests known to change state are refused.
These controls narrow what the plugin can do; none of them is a guarantee on its own. An administrator can still accept a more powerful login on purpose (audited and shown in status), root or Administrator on the host can replace the agent, and the plugin can read whatever its login can see.