release 1.7.3: monitoring pages as first-class suite section
README section lists public HTML report paths; sticky "What this monitors" adds a dedicated block that monpages/public pages are part of taler-monitoring.
This commit is contained in:
parent
ac6f90da35
commit
5f0ec6f638
5 changed files with 133 additions and 21 deletions
|
|
@ -192,3 +192,7 @@ Caddy `/var/www/monitoring-sites` is separate (you configured hernani write acce
|
|||
Host-agent jobs default to **`STRICT_EXIT=1`**: non-zero exit if suite checks fail, `DEPLOY_WWW_ROOT` is not writable, or public monpages (FQDN) fail.
|
||||
|
||||
Set `STRICT_EXIT=0` only if you want timers to stay green while still logging errors (not recommended for production).
|
||||
|
||||
## Monitoring pages (suite)
|
||||
|
||||
Public sticky-bar HTML under `/monitoring*` and `/taler-monitoring-*` is part of **taler-monitoring** (not a separate product). See main [README — Monitoring pages](../README.md#monitoring-pages-part-of-the-suite). Phase **monpages** verifies they are live.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue