[
https://issues.apache.org/jira/browse/HDDS-17819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-17819:
----------------------------------
Labels: pull-request-available (was: )
> Add OM metrics for committed key bytes by storage policy, storage tier and
> fallback outcome
> -------------------------------------------------------------------------------------------
>
> Key: HDDS-17819
> URL: https://issues.apache.org/jira/browse/HDDS-17819
> Project: Apache Ozone
> Issue Type: Task
> Reporter: Devesh Kumar Singh
> Assignee: Devesh Kumar Singh
> Priority: Major
> Labels: pull-request-available
>
> SCM marks each block it allocates with the tier it used and whether that tier
> was a fallback (isFallBack). OM stores both on every key location, but no
> metric exposes them. So an administrator cannot see how much new HOT data is
> landing on DISK because SSD is full.
> Add a counter of committed bytes with the labels policy, requestedTier,
> actualTier and outcome (preferred / fallback). Emit it where OM already
> counts committed bytes, so both stay consistent. The fallback share is
> computed in PromQL.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]