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 #2169 we discovered the logic for creating and assigning external segments/spans was cobbled together. We should provide convenience methods for capturing the necessary naming conventions for segments, and all of its necessary segment and span attributes.
Acceptance Criteria
As a Node.js engineer I should be able to call a convenience method to track an external http call as a segment with the appropriate attributes.
Additional Context
grpc instrumentation is in violation of what needs to be captured, this abstraction will help this out. undici and http-outbound are the other places external segments are captured
The text was updated successfully, but these errors were encountered:
Description
In #2169 we discovered the logic for creating and assigning external segments/spans was cobbled together. We should provide convenience methods for capturing the necessary naming conventions for segments, and all of its necessary segment and span attributes.
Acceptance Criteria
As a Node.js engineer I should be able to call a convenience method to track an external http call as a segment with the appropriate attributes.
Additional Context
grpc instrumentation is in violation of what needs to be captured, this abstraction will help this out. undici and http-outbound are the other places external segments are captured
The text was updated successfully, but these errors were encountered: