PHP-FPM¶

The phpfpm probe monitors a PHP-FPM pool via its JSON status page, reporting pool uptime, process counts, queue depth, slow request counts and aggregate request and connection statistics.

Quick start¶

# probes.d/20-php-fpm.yaml — each file under probes.d/ is a YAML array of probes
- name: phpfpm
  type: phpfpm
  params:
    endpoint: http://localhost/fpm-status

Parameters¶

Parameter	Must set	Default	Description
`endpoint`	In practice	`http://localhost/fpm-status`	URL of the pool status page, answering in JSON
`interval`	No	`60`	Seconds between collections
`timeout`	No	`10`	Request timeout in seconds
`instance_name`	No	-	Stable identity of this pool; set it when two phpfpm probes run on one host

The status page must answer in JSON: add ?json to the endpoint or configure the web server to pass it.

Metrics¶

Metric	Unit	Description
`senhub.phpfpm.up`	1	1 when the status endpoint is reachable
`phpfpm.uptime`	s	Seconds since the PHP-FPM pool started, tagged with `pool`
`phpfpm.accepted_connections`	{connection}	Total accepted connections since start
`phpfpm.listen_queue.current`	{connection}	Connections currently waiting in the listen queue
`phpfpm.listen_queue.max`	{connection}	Maximum observed listen queue length
`phpfpm.processes.active`	{process}	PHP-FPM worker processes currently serving a request
`phpfpm.processes.idle`	{process}	Idle worker processes
`phpfpm.process.count`	{process}	Total worker processes in the pool
`phpfpm.slow_requests`	#	Requests exceeding the slow request threshold (cumulative)
`phpfpm.slow_requests`	{request}	Requests that exceeded `request_slowlog_timeout`

Operational notes¶

Enable the status page in php-fpm.conf: pm.status_path = /fpm-status. The probe expects JSON output — configure Nginx or Apache to pass ?json automatically, or set the endpoint to include ?json.
For multi-pool setups, create one probe instance per pool, each pointing to its own pool's status URL.

Metric reference¶

Every metric this probe can emit. Metric is the OpenTelemetry name the OTLP, Prometheus and Zabbix outputs derive theirs from. Name is what a Nagios check and the API metrics= filter match. PRTG channel is the label PRTG shows, placeholders filled from the series' tags.

Metric	Name	PRTG channel	Unit	Description
`senhub.phpfpm.up`	`senhub.phpfpm.up`	PHP-FPM {pool} Up	#	1 when the PHP-FPM status endpoint is reachable, 0 otherwise
`phpfpm.uptime`	`phpfpm.uptime`	PHP-FPM {pool} Uptime	s	Number of seconds since the PHP-FPM pool started
`phpfpm.accepted_connections`	`phpfpm.accepted_connections`	PHP-FPM {pool} Accepted Connections	#	Total number of accepted connections since pool start
`phpfpm.slow_requests`	`phpfpm.slow_requests`	PHP-FPM {pool} Slow Requests	#	Total number of requests exceeding the slow request threshold
`phpfpm.listen_queue.current`	`phpfpm.listen_queue.current`	PHP-FPM {pool} Listen Queue	#	Current number of requests waiting in the listen queue
`phpfpm.listen_queue.max`	`phpfpm.listen_queue.max`	PHP-FPM {pool} Listen Queue Max	#	Maximum number of requests observed in the listen queue since pool start
`phpfpm.processes.active`	`phpfpm.processes.active`	PHP-FPM {pool} Active Processes	#	Number of active (currently serving requests) processes
`phpfpm.processes.idle`	`phpfpm.processes.idle`	PHP-FPM {pool} Idle Processes	#	Number of idle processes waiting for requests
`phpfpm.process.count`	`phpfpm.processes.total`	PHP-FPM {pool} Total Processes	#	Total number of processes (active + idle)
`phpfpm.max_children_reached`	`phpfpm.max_children_reached`	PHP-FPM {pool} Max Children Reached	#	Total number of times the max_children limit was reached since pool start