diff options
| author | batsumaru <> | 2026-07-01 16:52:22 +0900 |
|---|---|---|
| committer | batsumaru <> | 2026-07-01 16:52:22 +0900 |
| commit | a034c6724381b172ba4b6d36357682c44f18b8de (patch) | |
| tree | acb122f89c9432d56f3964c9a29d99ee1cf8647e /statuspage/README.md | |
| parent | bb3567aa4bd5d03fcd0fa74eea42381f159227b0 (diff) | |
Add pf visibility and a wg-quick watcher check, add a neutral row status
checks/pf.sh reports pf enabled/disabled, state table usage (warn/down
as it nears the configured limit), and the loaded filter/nat rule
count, then lists each active rule as its own row for at-a-glance
visibility into what's actually being enforced.
Those rule rows use a new "info" status (gray square) rather than
"ok" - they're not a health check on any individual rule, so a green
square there would misleadingly imply otherwise. render.sh maps
info -> gray; anything else still falls back to red.
checks/wg-watcher.sh checks the route-monitor process wg-quick spawns
to react to WAN interface/address changes - it isn't rc.d-managed, so
there's no `service status` for it, hence the new proc_running helper
in lib/common.sh (pgrep -f based).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Diffstat (limited to 'statuspage/README.md')
| -rw-r--r-- | statuspage/README.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/statuspage/README.md b/statuspage/README.md index 3b83a81..e77991a 100644 --- a/statuspage/README.md +++ b/statuspage/README.md @@ -36,7 +36,7 @@ Each JSON object has exactly these fields: | `section` | groups rows under a heading: `hardware`, `host services`, `jails` (or a new section name - unrecognized sections are rendered after the known ones, in the order first seen) | | `label` | display name for the row | | `value` | display value; use `""` for a plain up/down check with no value | -| `status` | one of `ok`, `warn`, `down` - maps to a green/yellow/red square | +| `status` | one of `ok`, `warn`, `down` (green/yellow/red), or `info` (gray) for a row that isn't a health signal at all - e.g. `pf.sh` lists loaded rules as `info` rather than implying each rule is itself being checked | Example (`checks/wireguard.sh`): |