docs: correct Ops, Fleet & Status in the beta README
spikersoft-backend@master SpikerSoft.EventHandlers.SystemRemediation/appsettings.Production.json:28 Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
1 parent
73e37252c7
commit
ffb442a8b9
1 file changed
+5
-5
@@ -2593,21 +2593,21 @@ This ensures `@spikersoft.com` emails (child account provisioning, notifications
|
|||||||
|
|
||||||
## Ops, Fleet & Status
|
## Ops, Fleet & Status
|
||||||
|
|
||||||
Beyond app-level health checks, the platform watches its own **host fleet** and surfaces incidents both to operators and to the public.
|
Beyond app-level health checks, the platform watches its own **host fleet**, shows incidents to operators, and shows a capability status rollup on the public page.
|
||||||
|
|
||||||
### Host-agent pipeline
|
### Host-agent pipeline
|
||||||
|
|
||||||
```
|
```
|
||||||
NodeAgent (1 per swarm node) SecurityMonitor SystemRemediation
|
NodeAgent (1 per swarm node) SecurityMonitor SystemRemediation
|
||||||
tails systemd journal → Redis-backed stateful → rule engine over events:
|
tails systemd journal → Redis-backed stateful → rule engine over events:
|
||||||
samples host health/disk detectors producing dedupes SystemIncident read-models,
|
samples host health/disk detectors producing dedupes SystemIncident read-models
|
||||||
→ publishes system.events SecurityAlerts dispatches a curated SAFE remediation
|
→ publishes system.events SecurityAlerts and alerts operators. Shipped
|
||||||
command back to the node, or alerts operators
|
posture is recommend-only
|
||||||
```
|
```
|
||||||
|
|
||||||
- `SpikerSoft.EventHandlers.NodeAgent` — journal tail + host health/disk sampling into `system.events`.
|
- `SpikerSoft.EventHandlers.NodeAgent` — journal tail + host health/disk sampling into `system.events`.
|
||||||
- `SpikerSoft.EventHandlers.SecurityMonitor` — stateful detectors (Redis-backed) that turn raw events into `SecurityAlert`s.
|
- `SpikerSoft.EventHandlers.SecurityMonitor` — stateful detectors (Redis-backed) that turn raw events into `SecurityAlert`s.
|
||||||
- `SpikerSoft.EventHandlers.SystemRemediation` — the rule engine; only **curated, safe** remediation commands are ever dispatched automatically.
|
- `SpikerSoft.EventHandlers.SystemRemediation` — the rule engine. It dedupes incidents and alerts operators. A SAFE command is dispatched only when `Remediation:Mode` is `auto` and `DispatchCommands` is true; production ships recommend-only.
|
||||||
|
|
||||||
### Ops console & public status
|
### Ops console & public status
|
||||||
|
|
||||||
|
|||||||
Reference in new issue
Block a user