mgr/prometheus doesn't expose used_bytes per pool
The current metrics exposed don't show actual space consumed within a pool (used_bytes) - so you have less data available to prometheus for alerting/monitoring than you do at the command line with ceph df detail
#2 Updated by Paul Cuzner about 1 month ago
- Status changed from New to Closed
Konstantin Shalygin wrote:
Can you explain?
Currently exporter have `ceph_pool_bytes_used` metric.
Apologies for the delay.
the parms in DF_POOL omit the used_bytes field, so although we can report in stored (ingested data), we can't see the actual consumed (used_bytes), which includes the effect of compression/ec/replication overheads