Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Semantic Convention for redundant connections #2470

Open
sirzooro opened this issue Apr 5, 2022 · 0 comments
Open

Semantic Convention for redundant connections #2470

sirzooro opened this issue Apr 5, 2022 · 0 comments
Labels
spec:trace Related to the specification/trace directory

Comments

@sirzooro
Copy link

sirzooro commented Apr 5, 2022

When system uses redundant connections, the same message is sent via multiple paths to destination. Current version of net.* attributes allows to specify single value only, so sender would have to create child span for every path in order to track all of them. I propose to extent them to allow using arrays too in addition to existing scalar string/int values. For example destination addresses could be reported as net.peer.ip = ["10.1.1.1", "10.2.2.2"].

You also could add recommendation that code should either use scalars value for all net.* attributes, or arrays with the same element count for all of them.

In my case message receiver drops duplicate messages and passes only one copy of them to upper layers, so existing set of net.* attributes are enough. However in general case it may be useful to use arrays on receiver side too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spec:trace Related to the specification/trace directory
Projects
None yet
Development

No branches or pull requests

2 participants