a1590f85ed
kb/runbooks/stability-agent-rollout.md — Deployment, Verification, Troubleshooting kb/subsystems/stability-agent-architektura.md — Architecture Summary + "Why UI only showed CHELSTY" Tresc sekcji nietknieta. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
24 lines
934 B
Markdown
24 lines
934 B
Markdown
---
|
|
okf: "0.1"
|
|
type: subsystem
|
|
visibility: private
|
|
status: active
|
|
updated: 2026-05-17
|
|
links:
|
|
- ../runbooks/stability-agent-rollout.md
|
|
---
|
|
|
|
# stability-agent — architektura rolloutu na flote
|
|
|
|
## Architecture Summary
|
|
The `stability-agent` is a lightweight Python service that monitors node health (disk, Docker containers, Tailscale, MQTT) and publishes state to a central Redis instance running on **PIHA**.
|
|
|
|
- **Source**: `services/stability-agent`
|
|
- **State Path**: `/opt/homelab/state`
|
|
- **Events Path**: `/opt/homelab/events`
|
|
- **Redis Target**: `100.108.208.3:6379` (PIHA)
|
|
|
|
## Why UI only showed CHELSTY
|
|
Previously, the `stability-agent` had `NODE_NAME` defaulted to `chelsty` and was only deployed there. The Agent System UI materializer on PIHA filters nodes based on the Redis keys `homelab:nodes:<NODE_NAME>`. Without other agents publishing their specific `NODE_NAME`, the UI remained limited to the single active node.
|
|
|