This is a demo with sample data.
Start free monitoring →
Graphs
worker-node.example.com
worker-node.example.com
Online • Last seen: Apr 11, 2026 12:01:27
NGINX Connections/s
accepted
dropped
NGINX Requests/s
requests
NGINX Current Connections
active
idle
NGINX HTTP Errors
4xx
5xx
Client Errors (4xx Breakdown)
403
404
Server Errors (5xx Breakdown)
500
502
503
504
Upstream Response Codes
2xx
4xx
5xx
HTTP Version Distribution
HTTP/1.0
HTTP/1.1
HTTP/2
HTTP/3
Request Time (avg)
request time
Upstream Response Time
connect
response
header
NGINX Cache
updating
bypass
expired
hit
miss
PHP-FPM Connections/s
accepted
PHP-FPM Connection Queue
current
max
PHP-FPM Processes
idle
active
total
PHP-FPM Slow Requests
slow requests
MySQL Connections/s
connections
MySQL Questions/s
questions
MySQL Queries
select
insert
update
delete
MySQL Threads
connected
running
CPU Usage %
user
system
Load Average
5 min
15 min
Memory (RAM)
total
used
Network Traffic
sent
received
Disk Usage
total
used
Disk I/O
read
write
Enable Varnish Monitoring
The agent needs read access to Varnish's shared memory file to collect cache metrics.
# Add the agent user to the varnish group
sudo usermod -aG varnish nginx
# Restart the agent to apply permissions
sudo systemctl restart amplify-agent
Why is this needed? The Varnish shared memory file (/var/lib/varnish/*/_.vsm) is readable by the varnish group. Adding the agent user to this group allows it to read statistics without elevated privileges.
Linked Websites
No websites linked
Monitor websites hosted on this server to correlate uptime with server metrics.
Add Website MonitorRecent Events
INFO
nginx config parsed, read from /etc/nginx/nginx.conf
Apr 11, 11:57:12
INFO
agent started, version 1.8.1-1
Apr 11, 11:47:12