Pro plan from £5 per endpoint per month · see pricing
Secronyx
AvailableLinuxWindowsmacOS

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.

# The least-privilege status endpoint for the nginx plugin. NGINX has no # users or roles: stub_status only shows counters, and the plugin reads # nothing else. The least privilege is a status location that only this # host can reach, on a server of its own so that redirects and rewrites # of your sites do not apply to it: # # 1. Put this in the http { } block, for example as # /etc/nginx/conf.d/secronyx-status.conf (Linux packages), # $(brew --prefix)/etc/nginx/servers/secronyx-status.conf (Homebrew) or # conf\secronyx-status.conf included from conf\nginx.conf (Windows). # 2. Check and reload: nginx -t && nginx -s reload # 3. Install with auth none (the default): secronyx plugin install <pack> # # Port 80 needs NGINX's master process to run as root (Linux packages # do); elsewhere use another port and install with --endpoint # 127.0.0.1:<port>. server { listen 127.0.0.1:80; server_name localhost; access_log off; location = /nginx_status { stub_status; allow 127.0.0.1; deny all; # Optional: also require a login, and install with --auth password # --allow-unchecked-privilege. Make the file with # htpasswd -c /etc/nginx/secronyx.htpasswd {{user}} # and use that login for nothing else. # auth_basic "secronyx"; # auth_basic_user_file /etc/nginx/secronyx.htpasswd; } }

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.