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

Apache HTTP Server

See whether every Apache worker is busy, how much traffic it is taking and what each worker is doing, from the read-only server status report.

What it answers

Questions an on-call engineer asks, which an AI client can answer with this plugin.

  • Are all Apache workers busy, and how many are idle?
  • How many requests and bytes per second is Apache serving?
  • Are workers stuck reading requests from slow clients, or sending slow replies?
  • When was Apache last restarted or reloaded?
  • How many worker slots are left before Apache refuses connections?

What it returns

Each of the plugin's read-only tools, described in words.

  • Apache httpd load in one row - busy, idle and graceful workers, requests and bytes per second, totals since restart, CPU load, uptime, config generation, MPM processes and connections
  • Apache httpd scoreboard in one row - how many worker slots are waiting, reading a request, sending a reply, in keep-alive, closing, logging, finishing gracefully or open, out of the total

At a glance

Plugin
apache 1.0.0
Publisher
levantar
Platforms
Linux, Windows, macOS

Tested on

  • Apache httpd 2.4.58, 2.4.62 and 2.4.71 on Linux (Ubuntu, Docker), CI runner
  • Apache httpd 2.4 on macOS (Homebrew), CI runner
  • Apache httpd 2.4.55 on Windows Server (Apache Lounge), 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 apache prints it; an administrator applies it by hand.

# The least-privilege login for the apache plugin. mod_status's report is # read-only and holds no request lines or client addresses in its ?auto # form. Apache has no roles: a login is as strong as the locations it can # reach. So serve /server-status to this host only, and keep # balancer-manager and server-info away from the plugin's login: the # privilege check refuses a login that reaches either. # # 1. Load mod_status (LoadModule status_module modules/mod_status.so) and # keep ExtendedStatus On (the default), for the traffic totals. # 2. Without a login (auth none), from this host only: <Location "/server-status"> SetHandler server-status Require local </Location> # 3. Or with a login (auth password, HTTP Basic), with a bcrypt hash from # htpasswd -B -c /etc/apache2/secronyx.htpasswd {{user}} # Use this instead of 2, not as well: # # <Location "/server-status"> # SetHandler server-status # AuthType Basic # AuthName "server-status" # AuthBasicProvider file # AuthUserFile "/etc/apache2/secronyx.htpasswd" # Require user {{user}} # </Location> # # 4. Do not grant this login (or, with auth none, this host) the # balancer-manager or server-info handlers.

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.