kotman12 commented on PR #3514: URL: https://github.com/apache/solr/pull/3514#issuecomment-3237350499
> Curious; have you run this in a debugger to get a sense of how the callback interacts with the system? I did when I was fiddling with this to try and trigger _all_ metrics. Btw we had callbacks before I moved it all to one batch callback .. in fact there were _more_ of them. This is the stack of the callback after calling metrics endpoint: ``` lambda$initializeMetrics$3:916, ReplicationHandler (org.apache.solr.handler) run:-1, ReplicationHandler$$Lambda/0x000079660082fc70 (org.apache.solr.handler) invokeCallback:84, CallbackRegistration (io.opentelemetry.sdk.metrics.internal.state) collectAll:124, SdkMeter (io.opentelemetry.sdk.metrics) produce:210, SdkMeterProvider$LeasedMetricProducer (io.opentelemetry.sdk.metrics) collectAllMetrics:234, SdkMeterProvider$SdkCollectionRegistration (io.opentelemetry.sdk.metrics) collect:61, PrometheusMetricReader (io.opentelemetry.exporter.prometheus) lambda$write$0:63, PrometheusResponseWriter (org.apache.solr.response) apply:-1, PrometheusResponseWriter$$Lambda/0x000079660094d6a8 (org.apache.solr.response) accept:273, ReferencePipeline$7$1 (java.util.stream) forEachRemaining:1787, HashMap$ValueSpliterator (java.util) copyInto:509, AbstractPipeline (java.util.stream) wrapAndCopyInto:499, AbstractPipeline (java.util.stream) evaluate:575, AbstractPipeline (java.util.stream) evaluateToArrayNode:260, AbstractPipeline (java.util.stream) toArray:616, ReferencePipeline (java.util.stream) toArray:622, ReferencePipeline (java.util.stream) toList:627, ReferencePipeline (java.util.stream) write:63, PrometheusResponseWriter (org.apache.solr.response) writeResponse:1012, HttpSolrCall (org.apache.solr.servlet) logAndFlushAdminRequest:921, HttpSolrCall (org.apache.solr.servlet) handleAdminRequest:904, HttpSolrCall (org.apache.solr.servlet) .... ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
