Skip to content

Conversation

thompson-tomo
Copy link
Contributor

@thompson-tomo thompson-tomo commented Oct 6, 2025

Fixes #2877
Closes #1721

Changes

Introduce a standalone guide on how to capture network addresses and what attributes to use when

Note: if the PR is touching an area that is not listed in the existing areas, or the area does not have sufficient domain experts coverage, the PR might be tagged as experts needed and move slowly until experts are identified.

Merge requirement checklist

  • CONTRIBUTING.md guidelines followed.
  • Change log entry added, according to the guidelines in When to add a changelog entry.
    • If your PR does not need a change log, start the PR title with [chore]
  • Links to the prototypes or existing instrumentations (when adding or changing conventions)

@thompson-tomo thompson-tomo requested review from a team as code owners October 6, 2025 03:56
@thompson-tomo thompson-tomo changed the title Introduce the network address guide #2877 [chore] Introduce the network address guide #2877 Oct 6, 2025
@thompson-tomo thompson-tomo force-pushed the editoral/#2877_RecordingNetwork branch 4 times, most recently from 4852536 to d666616 Compare October 6, 2025 04:24
@thompson-tomo thompson-tomo force-pushed the editoral/#2877_RecordingNetwork branch from d666616 to 8bc74f6 Compare October 6, 2025 04:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

Guide on recording network addresses Clarify difference between network.local.*/network.peer.* and source.*/destination.* attributes

1 participant