That's a nice start! I'd like to work with you on making the SIP better. Maybe a 1:1 (others invited too!) video might be most productive. I'd love to involve AB more here. I think the SIP template that you clearly started from isn't great; I'm tempted to replace it with a list of considerations and not a proposed format. People should structure their SIP however the topic best presents itself.
On Thu, Apr 17, 2025 at 2:34 PM Matthew Biscocho (BLOOMBERG/ 919 3RD A) < mbisco...@bloomberg.net> wrote: > Based on the discussion from yesterdays meetup, created SIP-23 for moving > to Open Telemetry > https://cwiki.apache.org/confluence/display/SOLR/SIP-23%3A+Switch+from+DropWizard+to+OpenTelemetry > > With Solr 10 around the corner, hoping this work can get done before then. > > From: dev@solr.apache.org At: 04/14/25 01:04:13 UTC-4:00To: > dev@solr.apache.org > Subject: Re: SIP proposal: Switch from DropWizard to OpenTelemetry > > I'm excited about the change! Where I work, it would *significantly* > simplify our metrics pipeline if Solr were to embrace OTel for metrics, as > we could then use company-provided OTel plugins. The broad industry > adoption of OTel points to this being the least friction. With DropWizard, > it appears we hacked attributes onto it, in a sense. > > The primary criteria/requirement that comes to mind is to have > strong/sophisticated ways to filter the right metrics to publish. Solr has > that today. > > On Fri, Apr 11, 2025 at 5:00 PM Matthew Biscocho (BLOOMBERG/ 919 3RD A) < > mbisco...@bloomberg.net> wrote: > > > Hey everyone, > > > > Making this thread because I was interested in writing up a SIP for > > SOLR-17458 https://issues.apache.org/jira/browse/SOLR-17458 and starting > > a discussion around this. The proposed change involves migrating Solr's > > metrics framework from DropWizard to OpenTelemetry (OTel). This will move > > Solr to an attribute based metric framework and will also help > > future-proofing by keeping it from vendor lock-in, given OpenTelemetry's > > stance on being vendor-neutral and working with many different pipelines. > > Since Solr already packages an Open Telemetry SDK as a module for > exporting > > spans through OTLP, we can use that foundation to have it push metrics as > > well. There will be a significant change here which will probably break > > many components and no longer be backwards compatible so this will > probably > > need to be a major release version change but we can potentially keep a > few > > things backwards compatible if needed. Just some things off the top of my > > head: > > > > * The Prometheus Exporter (Maybe should be deprecated?) > > * GET /admin/metrics endpoint > > * JVM metrics collected from OTel > > * Metric reporters? > > > > Anyone have thoughts? > > >
