NGINX
See how many connections NGINX holds, whether they are reading, writing or idle in keep-alive, and whether it is dropping any, from its stub_status page on this host.
What it answers
Questions an on-call engineer asks, which an AI client can answer with this plugin.
- How many connections is NGINX holding right now?
- Are requests piling up while NGINX writes responses?
- How many idle keep-alive connections are open?
- Is NGINX dropping connections it accepted?
- How many requests has NGINX served since it started?
What it returns
Each of the plugin's read-only tools, described in words.
- NGINX connection and request counters in one row - active connections, how many are reading a request, writing a response or idle in keep-alive, and accepted, handled and total requests
At a glance
- Plugin
- nginx 1.0.0
- Publisher
- levantar
- Platforms
- Linux, Windows, macOS
Tested on
- NGINX 1.26.3, 1.27.5, 1.30.6 and 1.31.8 on Linux (Ubuntu, Docker), CI runner
- NGINX from Homebrew on macOS, CI runner
- NGINX 1.30.6 on Windows Server (nginx.org build), CI runner
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)
- A user name and password
The least-privilege login
The setup file in the pack. secronyx plugin setup nginx prints it; an administrator applies it by hand.
See it run
Recording coming. Install, setup and status runs for this plugin are recorded on the shared test lab, and appear here once they have 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.