[
https://issues.apache.org/jira/browse/SOLR-17440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17879914#comment-17879914
]
David Smiley commented on SOLR-17440:
-------------------------------------
TBD on what such metrics should "look" like in terms of metadata.
All the /admin/collections ones should probably fall under the OVERSEER
registry, or maybe only some of them? BTW some actions are dispatched to the
Overseer (or happen via distributed cluster processing logic, which we can
pretend are the same for this comment), and some are processed on the receiving
node always like LIST. Hmm.
All the /admin/cores can be on the node registry
> Add metrics for /admin/collections and /admin/cores per ACTION
> --------------------------------------------------------------
>
> Key: SOLR-17440
> URL: https://issues.apache.org/jira/browse/SOLR-17440
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Components: metrics
> Reporter: David Smiley
> Priority: Major
>
> Solr has "handler" metrics (i.e. HTTP endpoints) for the most part. But (A)
> a number of operations for administering the Solr cluster are on two
> endpoints that are really dispatching endpoints based on an ACTION to a thing
> that doesn't have metrics. And (B) when "async" is used, we really want to
> measure the operation itself, not the HTTP endpoint, which will return
> trivially quickly in this case.
--
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
