39 lines
1.3 KiB
Markdown
39 lines
1.3 KiB
Markdown
# MinerOps v0.4: Monitoring
|
|
|
|
## Status
|
|
|
|
Planning document. The version label and candidate scope are provisional and do
|
|
not override the current version summary in `README.md` or phase ordering in
|
|
`docs/ROADMAP.md`.
|
|
|
|
## Goal
|
|
|
|
Provide reliable current-state and historical visibility across the fleet.
|
|
|
|
## Candidate Scope
|
|
|
|
- [ ] Configurable discovery
|
|
- [ ] MAC-based asset reconciliation
|
|
- [ ] Miner status and telemetry
|
|
- [ ] Historical retention
|
|
- [ ] Fleet dashboard
|
|
- [ ] Room, rack, model, and electrical summaries
|
|
- [ ] Alert generation and lifecycle
|
|
- [ ] Notification integrations
|
|
|
|
Discovery and network reconciliation depend on the roadmap's Inventory &
|
|
Identity phase, while electrical summaries depend on Infrastructure. Their
|
|
presence here does not change those dependencies.
|
|
|
|
The repository already contains early-stage discovery, telemetry, retention,
|
|
dashboard, and infrastructure-summary foundations. Unchecked items describe
|
|
work needed for a coherent, supported monitoring product rather than an absence
|
|
of related implementation.
|
|
|
|
## Definition of Done
|
|
|
|
Observations remain distinct from authoritative inventory, stale data is
|
|
explicit, discovery does not blindly create assets, retention is documented,
|
|
alerts are auditable, and monitoring failures cannot corrupt inventory or
|
|
repair history.
|