From 36d35b2a22609565245a8627c2552797f7196651 Mon Sep 17 00:00:00 2001 From: jester Date: Fri, 1 May 2026 18:25:22 +0000 Subject: [PATCH] Add monitoring Codex README --- Codex/Monitoring/README.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 Codex/Monitoring/README.md diff --git a/Codex/Monitoring/README.md b/Codex/Monitoring/README.md new file mode 100644 index 0000000..8b54809 --- /dev/null +++ b/Codex/Monitoring/README.md @@ -0,0 +1,25 @@ +# Monitoring Codex + +This folder tracks the ZeroLagHub monitoring and observability workstream. + +Monitoring implementation lives across infrastructure, API, Agent, Prometheus, Grafana, Alloy, and future log collection. This folder is the coordination layer for the monitoring contract, launch-readiness status, and validation plan. + +## Files + +- `CURRENT_STATE.md` — observed monitoring state and launch-readiness posture +- `CONTRACT.md` — intended monitoring/discovery/label contract +- `OPEN_ITEMS.md` — active monitoring blockers and follow-up work +- `VALIDATION.md` — smoke-test and acceptance checklist + +## Ownership boundary + +`zlh-grind` tracks coordination and decisions only. Implementation belongs in the relevant source/config locations: + +- `zpack-api` for monitoring discovery endpoints, health endpoints, app metrics, and auth boundaries +- `zlh-agent` for Alloy config/labels, structured logs, and container-local telemetry behavior +- monitoring host configuration for Prometheus, Grafana, Alloy, dashboards, firewall/bind policy, and file_sd sync +- infrastructure layer for OPNsense/PBS monitoring exceptions + +## Current launch posture + +As of the latest monitoring audit, monitoring is **not launch-ready**. Core services are running, but public exposure, stale/failing discovery, missing dashboards, and missing centralized logs block launch-debug readiness.