jester/zlh-grind
1
0
Fork 0
Code Issues 14 Pull Requests Actions Packages Projects Releases Wiki Activity

Add monitoring Codex README

Browse Source
This commit is contained in:
jester 2026-05-01 18:25:22 +00:00
parent 3ec13be4d5
commit 36d35b2a22
1 changed files with 25 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
Codex/Monitoring/README.md Normal file
View File

@ -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.