[
https://issues.apache.org/jira/browse/SOLR-17458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18035876#comment-18035876
]
Matthew Biscocho commented on SOLR-17458:
-----------------------------------------
{quote}
There is no way to synchronously start/stop the metrics recording??? Is there
are least a callback mechanism we can hook into to "wait" for the start/stop?
{quote}
There is not. I created a github issue to confirm with OTEL and they opened a
[PR
|https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/15231]opened
a fairly quickly which should solve this.
{quote}
Even if we choose to move the attributes to the context, it's still unclear
what it's {*}for{*}.
{quote}
I wrote a small javadoc on SolrMetricProducer that its just the base set of
attributes used for that implementing component initializing metrics (which
could be empty if they don't have any) but we can rethink and refactor how
those base set of attributes are binded to the instruments.
> 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
> Fix For: 10.0
>
> Time Spent: 3.5h
> 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]
