[
https://issues.apache.org/jira/browse/SOLR-17458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17940865#comment-17940865
]
David Smiley commented on SOLR-17458:
-------------------------------------
It'd be a huge code change, no doubt! Exciting :-D. I think outright
replacement is the way to go; it's too much maintenance/complexity to do both.
Major version only; it's not too late for 10. The metric naming is going to
change, yes. I think an LLM would be a perfect pairing for doing the
grunt-work any migration such as this. I'm not certain we'd need OTEL
->NamedList... it'd be fine to simply expose as Prometheus which is pretty
standard. We'd want lots of the filter-ability Solr currently offers to only
expose needed metrics.
This is very SIP-worthy, which means writing about the change in the big
picture; what we'd gain, what would change, what we might loose (negotiable).
BTW I have an old-ish PR renovating tracing in 10 that might intersect with
this. I recommend avoiding touching tracing here until I finish that; probably
not an issue.
> 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
> Priority: Major
>
> 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]
