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
Hi. I'm quite new to a telemetry concepts. As I understand we can organize a hierarchical span context tree along some process.
And so Is there any way to join the spans in correlated sub spans?
In my case there's a set of input signals. Each has a personal computational pipeline. So that it looks like logically it is one span tree per each pipeline.
But at some point the pipelines are joined for batch processing. So what is the common practice would be suitable here?
Should I just for pipeline of pipelines {pipeline.child('batching', {attributes: {batchId}])}
Or is there any Span Grouping/Overlapping/Mixing/Composing native concept
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi. I'm quite new to a telemetry concepts. As I understand we can organize a hierarchical span context tree along some process.
And so Is there any way to join the spans in correlated sub spans?
In my case there's a set of input signals. Each has a personal computational pipeline. So that it looks like logically it is one span tree per each pipeline.
But at some point the pipelines are joined for batch processing. So what is the common practice would be suitable here?
for pipeline of pipelines {pipeline.child('batching', {attributes: {batchId}])}
Thx.
Beta Was this translation helpful? Give feedback.
All reactions