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

Matthew Biscocho commented on SOLR-17458:
-----------------------------------------

So the /metrics endpoint becomes prometheus only? I can get behind that. Otel 
also supports a `otel.metrics.exporter=prometheus` to bind the metric server to 
a different port if people want to go that direction. Maybe out of scope for 
now. But with move to OTEL for the metrics endpoint, that also means the 
deprecation of prometheus exporter unless we want to refactor into something 
new. Configurability to make new metrics? I don't think the maintenance and 
work of the prometheus exporter is worth it and just push users to use 
something else such as the OTEL collector to move metrics to their preferred 
monitoring system/vendor or some existing solution like 
[Telegraf|https://github.com/influxdata/telegraf] if they really want some kind 
of pre-aggregation filtering or do something really custom.

What exactly are you renovating in tracing? I am taking advantage of the 
existing Opentelemetry module that exports OTLP included in Solr already and 
going to be making small modifications to it so it accepts metrics and it's not 
just advertised as a tracing module.

Happy to write a SIP on the side. Open Telemetry is documentation is a monster 
so still learning the in and outs with what we can do. Is there a way to make a 
confluence account so I can start a write up? Or maybe need to start a 
discussion on DEV mailing list first.

> 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: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org

Reply via email to