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
Is your feature request related to a problem? Please describe.
Traces coming from the otel-trace-pipeline and forwarded to the service-map-pipeline don't propagate some items. It could be a great improvement if custom items could be added in the service-map-pipeline.
Describe the solution you'd like
The trace I recieve at the moment from the service-map-pipeline is the following:
This trace should be manipulated such that a "tenant" item is added. "tenant" is already available as a resource attribute within the trace in the otel-trace-pipeline :
Is your feature request related to a problem? Please describe.
Traces coming from the otel-trace-pipeline and forwarded to the service-map-pipeline don't propagate some items. It could be a great improvement if custom items could be added in the service-map-pipeline.
Describe the solution you'd like
The trace I recieve at the moment from the service-map-pipeline is the following:
This trace should be manipulated such that a "tenant" item is added. "tenant" is already available as a resource attribute within the trace in the otel-trace-pipeline :
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: