Customers using Grafana dashboards are confused by bytes_sent and bytes_received metrics — they expect a single aggregate across all protocols (HTTP, MQTT, WebSocket) but the current behavior reports per-protocol. The docs only say "Bytes sent/received by protocol" without explaining the implications.
Two-part ask
1. Documentation update — make the per-protocol nature explicit and document how to aggregate in Grafana:
sum by (instance) (harperdb_bytes_sent)
Clarify what protocol label values to expect and what each represents.
2. Consider whether to add a total/aggregate metric — an optional harperdb_bytes_total{direction="sent"} style metric that already aggregates could reduce Grafana confusion. Evaluate if worth adding alongside the per-protocol ones.
🤖 Filed by Claude on behalf of Kris.
Customers using Grafana dashboards are confused by
bytes_sentandbytes_receivedmetrics — they expect a single aggregate across all protocols (HTTP, MQTT, WebSocket) but the current behavior reports per-protocol. The docs only say "Bytes sent/received by protocol" without explaining the implications.Two-part ask
1. Documentation update — make the per-protocol nature explicit and document how to aggregate in Grafana:
Clarify what
protocollabel values to expect and what each represents.2. Consider whether to add a total/aggregate metric — an optional
harperdb_bytes_total{direction="sent"}style metric that already aggregates could reduce Grafana confusion. Evaluate if worth adding alongside the per-protocol ones.🤖 Filed by Claude on behalf of Kris.