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
In our otel bridge span processor we have logic to reconcile span attributes with the appropriate names of the segment attributes. Even though when we create spans from segments, we need to ensure the expected segment attributes exist. This requires a little digging. There is mapping logic in lib/spans/span-event.js for generic spans(which this gets assigned). But you will also need to look at the instrumentation for message shim consumption. Since these spans create transactions we also have to end the transaction when the span ends.
Note: We assign generic as the span kind. We should enhance to assign the appropriate kind
The text was updated successfully, but these errors were encountered:
Description
In our otel bridge span processor we have logic to reconcile span attributes with the appropriate names of the segment attributes. Even though when we create spans from segments, we need to ensure the expected segment attributes exist. This requires a little digging. There is mapping logic in
lib/spans/span-event.js
for generic spans(which this gets assigned). But you will also need to look at the instrumentation for message shim consumption. Since these spans create transactions we also have to end the transaction when the span ends.Note: We assign generic as the span kind. We should enhance to assign the appropriate kind
The text was updated successfully, but these errors were encountered: