capistrant commented on code in PR #20199: URL: https://github.com/apache/druid/pull/20199#discussion_r3897332627
########## docs/operations/metrics.md: ########## @@ -469,7 +469,9 @@ These metrics are emitted by the Druid Coordinator in every run of the correspon |`tier/historical/count`|Number of available historical nodes in each tier. The `tierAlias` dimension is emitted only when the tier belongs to an alias configured via [`historicalTierAliases`](../configuration/index.md#dynamic-configuration), and can be used to aggregate metrics across the tiers in an alias.|`tier`, `tierAlias`|Varies| |`tier/replication/factor`|Configured maximum replication factor in each tier. The `tierAlias` dimension is emitted only when the tier belongs to an alias configured via [`historicalTierAliases`](../configuration/index.md#dynamic-configuration).|`tier`, `tierAlias`|Varies| |`tier/required/capacity`|Total capacity in bytes required in each tier. The `tierAlias` dimension is emitted only when the tier belongs to an alias configured via [`historicalTierAliases`](../configuration/index.md#dynamic-configuration).|`tier`, `tierAlias`|Varies| -|`tier/total/capacity`|Total capacity in bytes available in each tier. The `tierAlias` dimension is emitted only when the tier belongs to an alias configured via [`historicalTierAliases`](../configuration/index.md#dynamic-configuration).|`tier`, `tierAlias`|Varies| +|`tier/total/capacity`|Total capacity in bytes available in each tier. Can be greater than physical disk capacity if using virtual storage. The `tierAlias` dimension is emitted only when the tier belongs to an alias configured via [`historicalTierAliases`](../configuration/index.md#dynamic-configuration).|`tier`, `tierAlias`|Varies| Review Comment: `tier/storage/used` I fully agree with. that is better name than I had, wil change. I am considering something like `tier/storage/assignableCapacity` as the replacement for deprecated `tier/total/capacity`. It is what the coordinator sees as the amount of data it can assign to a tier. then leaving `tier/storage/capacity` as is to reduce metric name churn? thoughts? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
