[
https://issues.apache.org/jira/browse/SOLR-17458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18035454#comment-18035454
]
Chris M. Hostetter commented on SOLR-17458:
-------------------------------------------
{quote}... but in the OpenTelemetry library that we are using, it starts that
recording on a separate thread...
{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}In general, I had JVM metrics disabled on all tests except ones that
used them for SolrTestCaseJ4 but this test bypassed that in that it extended
SolrTestCase directly. We can disable JVM metrics here as well since this test
doesn't use them.
{quote} # This isn't the only test that uses SolrTestCase
# Disabling metrics except in tests that explicitly "check" metrics sounds
like a surefire way to be confident we are hiding metrics related errors from
ourselves.
> 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: 3h 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]
