Harden production workflows and agent admission

This commit is contained in:
Stanislav Rossovskii
2026-05-28 14:19:27 +04:00
parent a2e88b4e76
commit 37b1a1d6d6
109 changed files with 4927 additions and 894 deletions

View File

@@ -6,13 +6,13 @@ It is split into three independent applications:
- `agent/` - a small Go binary installed on monitored hosts.
- `server/` - a Python/FastAPI backend that owns inventory, state, incidents, and notifications.
- `web/` - a read-only Next.js dashboard.
- `web/` - a Next.js dashboard with agent admission controls.
The first project phase is documentation and planning bootstrap only. Core business logic is intentionally not implemented yet.
All three applications are implemented and run together via Docker Compose. The current release covers agent ingestion with operator admission, server-owned incident lifecycle and notifier outbox, a Next.js dashboard, and partitioned event retention.
## MVP
## Scope
Monlet v1 focuses on local checks, central state, and simple read-only visibility:
Monlet v1 focuses on local checks, central state, and simple visibility:
- agents run local checks from TOML config;
- agents expose Prometheus metrics and/or push facts to the server;
@@ -39,9 +39,9 @@ Monlet v1 focuses on local checks, central state, and simple read-only visibilit
- `docs/` - architecture, ADRs, development, and operations docs.
- `plan/` - stage workflow and exit checkpoints.
- `api/` - versioned OpenAPI contract.
- `agent/` - Go agent placeholder and deployment notes.
- `server/` - Python backend placeholder.
- `web/` - Next.js frontend placeholder.
- `agent/` - Go agent: scheduler, runner, spool, metrics.
- `server/` - Python/FastAPI backend: ingestion, detector, notifier outbox.
- `web/` - Next.js dashboard and agent admission UI.
- `deploy/` - local and observability deployment examples.
- `examples/` - example checks and configs.
@@ -59,4 +59,4 @@ Read in this order:
## Current Status
Stage 0 is the only active stage: documentation bootstrap. Do not start agent, server, or web core logic until Stage 0 exits and the API contract is reviewed.
Active development. Stages 06 are implemented. Run the stack via `docker compose up --build` from `deploy/`. See `docs/operations/deployment.md` and `docs/ops/` runbooks.