AWSXRay.config(): confusing calls to segmentUtils.setOrigin() overwrite each other
Open
enhancement
- Dominant language
- JavaScript
- Stars
- 280
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/aws/aws-xray-sdk-node/blob/6d356678de8d7214ba67a2f37291e71de818e45a/packages/core/lib/aws-xray.js#L56-L67
Reading through this I noticed that while each plugin provides an `originName`, and `setOrigin` is called per plugin, the segmentUtils actually only have a single `origin` -- IOW the origin of the last plugin wins. This is a bit confusing/unexpected to me.
Contributor guide
Assessment
This issue has not been assessed yet.