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

Clarify difference between network.local.*/network.peer.* and source.*/destination.* attributes #1721

Open
evan-bradley opened this issue Jan 6, 2025 · 0 comments

Comments

@evan-bradley
Copy link
Contributor

Area(s)

area:destination, area:network, area:source

Is your change request related to a problem? Please describe.

The docs for the network semantic conventions, source attributes, and destination attributes don't make it clear how network.local.*/network.peer.* and source.*/destination.* relate to each other.

The sense I get from the docs is that the network semconv attributes should be used in things like traces where a service is reporting on its own network communications, versus the source/destination attributes, which should be used by third-party services recording network transmissions between other applications.

Describe the solution you'd like

Clearly define the relationship between the two sets of attributes and advise in the docs when one or the other should be used.

Describe alternatives you've considered

No response

Additional context

I'm assisting the development of a Collector receiver that consumes NetFlow messages, and it isn't entirely clear to me how to translate the fields in NetFlow payloads to attributes in our semantic conventions given these two sets of attributes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant