You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Jaeger exporter does not currently export Resources. It comes close to exporting them as process tags here.
This is somewhat more complicated than it should be, because the specification allows for multiple tracer providers, where each can have different resources, but be hooked up to the same export pipeline. See here for more commentary. If we follow the spec, resources do not necessarily have a 1-1 relationship with processes, and that makes it difficult to add resource labels as Jaeger process tags.
We have two options (possibly more) that we can consider:
We could ignore the multiple tracer provider use case, and use the Resource from the global TracerProvider, and add its attributes as process tags.
Other languages (Python and Go) merge resource labels into span attributes rather than exporting them as process tags. We could decide to do the same. See:
For what it’s worth, I like the idea of being consistent across languages. With that in mind, merge resource labels into span attributes makes sense to me.
I think this approach makes more sense. If we're going to support multiple tracer providers, we should group spans for export by Resource and export each group as a batch with the Resource encoded as the process.
I'm flexible about how we solve this, but think that we should aim for consistency across languages. I opened a spec issue for discussion: open-telemetry/opentelemetry-specification#848.
The Jaeger exporter does not currently export Resources. It comes close to exporting them as process tags here.
This is somewhat more complicated than it should be, because the specification allows for multiple tracer providers, where each can have different resources, but be hooked up to the same export pipeline. See here for more commentary. If we follow the spec, resources do not necessarily have a 1-1 relationship with processes, and that makes it difficult to add resource labels as Jaeger process tags.
We have two options (possibly more) that we can consider:
The text was updated successfully, but these errors were encountered: