[ 
https://issues.apache.org/jira/browse/SOLR-17458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18020117#comment-18020117
 ] 

David Smiley commented on SOLR-17458:
-------------------------------------

There was some feedback at the CoC conference presentation that we're going to 
lose some convenience metrics due to the change of philosophy of the 
frameworks.  I'd love to see an example of that (say on RequestHandler) in this 
JIRA so we're clear.  The response was that other metrics infrastructure 
connected to this (OTLP Collector?) will do this so you'll still get what you 
need by the time it's visualized in Grafana.  Butnonetheless, someone just 
running Solr (even a developer scenario) will not see this info.  To somewhat 
address that need, I wonder if there's a standalone Docker container or Docker 
compose of containers that would ~easily allow someone to visualize metrics in 
Grafana from Solr 10?  That would be super nice.

> Metrics: switch from DropWizard to OpenTelemetry
> ------------------------------------------------
>
>                 Key: SOLR-17458
>                 URL: https://issues.apache.org/jira/browse/SOLR-17458
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Matthew Biscocho
>            Assignee: Matthew Biscocho
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Solr currently captures metrics with Dropwizard 4. There was some limitations 
> to Dropwizard, biggest one being metrics without tags/attributes making 
> aggregation difficult and requires the Prometheus Exporter to work with 
> Grafana.
> Creating this to track and explore integrating OpenTelemetry into Solr and 
> possibly replace Dropwizard giving a larger exposure of observability tools.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to