hashgraph / hashgraph/solo-weaver
Story 4.4 — Export nft counters to Prometheus; document Hubble-visibility loss
- Dominant language
- Go
- Stars
- 3
- Forks
- 0
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 46
Description
**Epic:** #740 — Validation, rollback & observability
Design: [v4 design](https://github.com/automa-saga/traffic-shaper/blob/main/docs/bn-qos-multiclass-priority-design-v4-nft-priority.md) §10 risk 9.
Expose per-rule/per-class nft counters to Prometheus, replacing the Hubble flow visibility forfeited by not using CiliumNetworkPolicy.
**Acceptance criteria:**
- Export nft counters (per class / per category) to Prometheus.
- Document `nft monitor` for ad-hoc debugging.
- Document the loss of Hubble flow visibility and the counter-based replacement.
Contributor guide
Research direction
Read docs/bn-qos-multiclass-priority-design-v4-nft-priority.md §10 risk 9, then trace the existing nft rule/counter and Prometheus metric entry points. Done means per-class and per-category nft counters are exported, and the documentation covers `nft monitor`, the lost Hubble flow visibility, and the counter-based replacement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, prometheus
- Domain
- networking, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100