[
https://issues.apache.org/jira/browse/IGNITE-28795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18097093#comment-18097093
]
Ignite TC Bot commented on IGNITE-28795:
----------------------------------------
Docs Required cleared. PR #13247 was merged as
548f36cbbd717d1ddfe14eddeb1449787524b6b3 and documents SizeUsedByData in
docs/_docs/monitoring-metrics/new-metrics-system.adoc and
docs/_docs/monitoring-metrics/new-metrics.adoc. Release Notes Required is left
unchanged.
> [doc] Document SizeUsedByData metric for data region monitoring
> ---------------------------------------------------------------
>
> Key: IGNITE-28795
> URL: https://issues.apache.org/jira/browse/IGNITE-28795
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
> Reporter: Ignite TC Bot
> Assignee: Ignite TC Bot
> Priority: Major
> Labels: docs-ux, ise
> Fix For: 2.18, 2.19
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The SizeUsedByData metric is available in the io.dataregion.{region_name}
> registry, but it is not described in the user documentation.
> Current docs explain data region monitoring through TotalAllocatedSize,
> PagesFillFactor, TotalUsedPages, PhysicalMemoryPages, and PhysicalMemorySize,
> and the control.sh metric example for io.dataregion.default does not include
> SizeUsedByData.
> This follow-up should document:
> - what SizeUsedByData represents
> - how it differs from TotalAllocatedSize, OffheapUsedSize, and
> PhysicalMemorySize
> - how to use it when monitoring data region usage
> - the updated io.dataregion metric listing and control.sh example output
> Related implementation origin: IGNITE-17728 Improve data size-related metrics.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
