Overview
breakdown
Storage retention · this node
Waiting for a background sample…
Approximate file accounting under this node’s Stroma root. Unix samples use allocated file blocks and count hard links once, preferring active data. Directory blocks, filesystem metadata, reflink sharing and files outside this root are excluded. Current logs can include segments pinned by a checkpoint. Retained bytes are not automatically safe to delete.
Throughput — last 30 min
published / s delivered / s
History lives in memory and starts with the broker - a few samples in, the lines appear.
Needs attention
Backlog — last 30 min --
Ready messages across every queue. The trend says whether consumers are draining or falling behind - more useful than any single gauge.
Nodes
Registered brokers with their live load. The cluster page has the full picture.
| Node | Address | Status | Owns | Publish / s | Delivered / s |
|---|
Resources — last 30 min (memory, CPU, disk)
Memory, MB
CPU
Disk, MB
Stroma Timings
Queue actor delay, durable event appends, and snapshot cost.
- Event append
- --
- Max queue wait
- --
- Max queue work
- --
- Snapshot total
- --
Stroma Health
Compact storage-engine signals. Use Diagnostics for details.
| Queue actor backlog | -- |
| Event appends / s | -- |
| Event bytes written | -- |
| Snapshot attempts | -- |
| Last snapshot size | -- |
| Recovered queues | -- |
Reconnects
Compact session continuity signals since broker start.
- Resumed
- --
- Rejected
- --
- Grace expired
- --
- Reconciled subs
- --
Detailed reconnect counters
| Grace entered | -- |
| Subscriptions kept | -- |
| Subscriptions restored | -- |
| Client streams closed | -- |
| Server subscriptions dropped | -- |