[
https://issues.apache.org/jira/browse/SOLR-15007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17599603#comment-17599603
]
ASF subversion and git services commented on SOLR-15007:
--------------------------------------------------------
Commit 2e2473dc2185af5731bc5a816a2e632d81ab7005 in solr's branch
refs/heads/branch_9x from Justin Sweeney
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=2e2473dc218 ]
SOLR-15007: Aggregated node level metrics for request handlers (#948)
Useful when there are lots of cores.
Co-authored-by: Justin Sweeney <justinswe...@fullstory.com>
> Aggregate core handler=/select and /update metrics at the node level metric
> too
> -------------------------------------------------------------------------------
>
> Key: SOLR-15007
> URL: https://issues.apache.org/jira/browse/SOLR-15007
> Project: Solr
> Issue Type: Wish
> Components: metrics
> Affects Versions: 9.0
> Reporter: Mathieu Marie
> Priority: Minor
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> At my company, we anticipate huge number of cores and would like to report
> aggregated view at the node level instead of the core level that will grow
> exponentially.
> Right now, we're aggregating all of the solr.cores metrics to compute
> per-cluster dashboards.
> But given that there are many admin handlers already reporting metrics at the
> node level, I wonder if we could aggregate _/update_, _/select_ and all the
> other handler counters in solr and expose them at the solr.node level too.
> It would requires (a lot) less data to transport, store and aggregate later,
> while still giving access to per core metrics.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
