Albert

> @albertteoh do you have rights for https://docs.github.com/en/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository ? Nice, seems like I do 😄 Thanks for the tip, @delanym!

@Leena1666 it's yours!

> Hi @albertteoh did you manage to fix that? Hi @rodrigorodrigues, sorry, I haven't looked into this for a long time and, from what I recall, I didn't get it...

@Bruno-DaSilva @forestsword @greut the bug indeed hasn't yet been fixed and https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/11149 was just a speculative attempt at a fix without being able to reproduce the problem reliably, or perhaps...

> I wish there was more trace information from Jaeger query. For instance including the ES request that has been made? With all due respect, the tracing information from Jaeger...

BTW, this doesn't reflect all the ES queries made, it's just the first query to fetch traces. Jaeger will then make follow-up requests to fetch spans, which is probably the...

> I'm still curious if Jaeger hits the same index. As I use aliases with a read alias, because rollover. Now I've got something to test out, why Elastic is...

SPM tab supports querying metrics on span kind; if you're capturing client spans, you should be able to see these error metrics in SPM. Otherwise, if we're not collecting client...

> Being archived is not a strong reason to migrate off of by itself I appreciate the response @Quinn-With-Two-Ns and yes, I agree, it's not a strong reason to migrate...

@jpkrohling ☝🏼