Emil Kleszcz created HDDS-15333:
-----------------------------------

             Summary: Expose volume quota and namespace usage metrics in OM 
Prometheus endpoint
                 Key: HDDS-15333
                 URL: https://issues.apache.org/jira/browse/HDDS-15333
             Project: Apache Ozone
          Issue Type: Improvement
    Affects Versions: 2.1.0, 2.0.0
            Reporter: Emil Kleszcz


Apache Ozone exposes bucket quota metrics from OM via /prom, for example:

bucket_utilization_metrics_bucket_used_bytes
bucket_utilization_metrics_bucket_quota_bytes
bucket_utilization_metrics_bucket_available_bytes
bucket_utilization_metrics_bucket_quota_namespace

These are useful for bucket byte quota monitoring, but there appear to be no 
equivalent Prometheus metrics for native volume quotas, even though volume 
quotas are available via the CLI/API.

Example CLI output:

ozone sh volume list

volume            quotaInBytes     quotaInNamespace
batch-accounting  1099511627776    -1
monitoring        10995116277760   -1
user              -1               -1

Also, for buckets, the CLI exposes namespace usage:

ozone sh bucket info /user/ekleszcz

usedNamespace: 4
quotaInNamespace: 10

but OM /prom appears to expose only the namespace quota limit:

bucket_utilization_metrics_bucket_quota_namespace

and not a matching used namespace metric.

This makes it possible to monitor bucket byte quota usage, but not:
- native volume quota usage
- volume quota limits via Prometheus
- bucket namespace quota usage percentage

Requested improvement:

Expose OM Prometheus metrics for:
- volume used bytes
- volume quota bytes
- volume available bytes, if applicable
- volume namespace quota
- volume used namespace
- bucket used namespace

This would allow operators to build Grafana dashboards and alerts for both 
volume and bucket quota usage without relying on custom exporters or CLI 
polling.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to