Apache9 commented on pull request #2748: URL: https://github.com/apache/hbase/pull/2748#issuecomment-745689175
> I don't seem to be able to find the "In-Memory Exporter: keeps the data in memory, useful for debugging." in the OTel codebase (need to look harder I suppose) Hopefully its a circular buffer. Could do basic dump into a jsp page of most recent traces. Without some sort of visualization, its hard to know what we are capturing. > It has been moved to sdk-testing https://github.com/open-telemetry/opentelemetry-java/blob/master/sdk/testing/src/main/java/io/opentelemetry/sdk/testing/exporter/InMemorySpanExporter.java So I think the intenion here is to not use it in production, only when testing. We could write our own implementation of SpanExporter to receive and show it on our web page but I still think it will be better to just use an external service to process the trace data. There are already lots of tracing systems in the world, in ASF we have two, zipkin and skywalking, so for me I'm not in favor of implementing a tracing page by our own, but anyway I'm not going to stop others if they want to :) > Can figure this out later. Yes, as said in the past, we could do this in parallel when implementing tracing in HBase code. It is all about how to export the tracing data. > > For sure all aboard for OTel? We are decided? Hadoop is going that way too? If so, +1. For me, as long as OpenTelemetry could connect with different tracing systems, and is the succesor of OpenTracing, I do not see any other choice, unless we want to tie with a specific tracing system, i.e, zipkin, jaeger, or skywalking. And for Hadoop, @jojochuang has opened several issues to use OpenTracing instead of HTrace, at the same time when he opened issues in HBase. And there is no progress for a while recently, I think we could talk to him to see if hadoop could also switch to use OpenTelemetry instead. Hope this could solve your concern. Thanks. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
