Web servers
Monitor Nginx, Apache, Caddy and PHP-FPM
Connections, workers and upstreams, read by the agent you already run.
Each server, measured as itself
Nginx, Apache and PHP-FPM are monitored as themselves, not guessed from CPU. The agent reads each one’s own status and shows it next to the rest of the host.
- Caddy works out of the box through its admin API
- Nginx needs its status page turned on
- No exporter to install or maintain
- On the same timeline as CPU, memory and disk
The layer your users hit first
Know whether the web tier is the bottleneck, not just the server under it.
Nginx
Active connections, plus the ones reading, writing and waiting.
Apache
Requests per second, throughput, busy and idle workers.
PHP-FPM
Active and idle processes, listen queue, max children reached and slow requests.
Caddy
Healthy and unhealthy upstreams, requests, failures and TLS policies.
No exporter
The same agent that watches the server reads the web stack.
Next to the host
Spot whether a slow site comes from the web server or from the machine.
Frequently asked questions
Nginx, Apache, Caddy and PHP-FPM.
Caddy works as is, since its admin API is on by default. Nginx needs its stub_status page turned on.
No. The Fivenines agent on the host collects everything.
Nginx, Apache and Caddy work wherever the agent runs. PHP-FPM metrics are collected on Linux.
Yes. Each service shows on its host, on the same timeline as CPU, memory and disk.
Something else on your mind? Talk to us →