Albert

> @jpkrohling @albertteoh Thanks again. Addressed the review comments Are you able to answer @jpkrohling's question: https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/12421#discussion_r925995997? I'm quite curious about how and why service-name routing is used.

> does this clarify? Yup, makes sense now, thanks @vjsamuel. I wonder if prometheus federation would help in this case (I have zero experience with it, but just heard about...

Thank you very much @MrAlias @Aneurysm9! I did try upgrading otel-go to pick up those recent changes, which sound promising as indeed, all I want to achieve is to simply...

Relates to: https://github.com/jaegertracing/documentation/issues/325

This sounds reasonable to me as Jaeger doesn't provide functionality to search in log fields, just tags and I believe this is where the [benefits of nested fields](https://www.elastic.co/guide/en/elasticsearch/reference/current/nested.html#nested-fields-array-objects) lay. As...

Thanks for the correction @yurishkuro @bhiravabhatla :)

> This would imply the trace would be returned if the key,value mentioned tags matches any of the logs field key/value pairs as well. @bhiravabhatla yes, that's correct. For example,...

@bhiravabhatla This was before my time, so I'll defer to the more experienced members of the community on this question. I agree though that Jaeger UI's search field for this...

@bhiravabhatla I'd agree that ideally there should be consistent behaviour across all backends, and perhaps this inconsistency was due to limitations in later introduced backends that couldn't meet the requirements....

Although, having the API expose capabilities may be useful for some use cases like the one mentioned in the [jaeger channel relating to searches across services](https://cloud-native.slack.com/archives/CGG7NFUJ3/p1624977898306100). In this case, if...