[
https://issues.apache.org/jira/browse/SOLR-17799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley resolved SOLR-17799.
---------------------------------
Fix Version/s: main (10.0)
Resolution: Fixed
> Revamp segment merge metrics
> ----------------------------
>
> Key: SOLR-17799
> URL: https://issues.apache.org/jira/browse/SOLR-17799
> Project: Solr
> Issue Type: Improvement
> Reporter: Kevin Liang
> Priority: Minor
> Labels: pull-request-available
> Fix For: main (10.0)
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> Based on current
> [documentation|https://solr.apache.org/guide/solr/latest/deployment-guide/metrics-reporting.html#index-merge-metrics]
> for segment merge metrics, there are two major groups of metrics emitted
> (for currently actively running merges and for merges that have completed).
> The actively running ones are gauges that can go up or down, while the ones
> for completed are counters/timers.
> To make these metrics more consistent and aggregate-able, propose emitting
> all metrics for merges as running counters for # of merges, # of segments,
> and # of documents with a metric for each tracking started/completed (thus
> active merges can be calculated via the current diff between the two).
> Relates to original feature from
> https://issues.apache.org/jira/browse/SOLR-9854
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
