[
https://issues.apache.org/jira/browse/SOLR-13979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16987519#comment-16987519
]
Shawn Heisey commented on SOLR-13979:
-------------------------------------
My old solution for this, on systems NOT running in cloud mode, was to define
an aggregation core which had the shards parameter defined in solrconfig.xml.
Relevant stats were found by looking at the /search handler on that core. I
also defined a special handler on every core which was used by ping health
checks and other miscellaneous automated uses so that those requests would not
impact stats for real queries.
Does SolrCloud keep separate stats for requests sent to the collection name
rather than a specific shard/core? If not, I think it should. I have no idea
how to implement such a thing.
> Expose separate metrics for distributed and non-distributed requests
> --------------------------------------------------------------------
>
> Key: SOLR-13979
> URL: https://issues.apache.org/jira/browse/SOLR-13979
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: metrics
> Reporter: Shalin Shekhar Mangar
> Priority: Major
> Fix For: master (9.0), 8.4
>
>
> Currently we expose metrics such as count, rate and latency on a per handler
> level however for search requests there is no distinction made for distrib vs
> non-distrib requests. This means that there is no way to find the count, rate
> or latency of only user-sent queries.
> I propose that we expose distrib vs non-distrib metrics separately.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
