Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Document `(client|server).socket.(address|port)` and the attributes that supercede it

Open
  • Is something wrong?
#17 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
documentation

Research direction

Read the linked semantic-conventions PR and the OpenTelemetry network attributes registry first, then locate this repository's migration documentation and changelog entry points. Done means the removed socket attributes, their replacement network attributes, and the deprecated net.sock attributes are documented with the relevant migration guidance.

Written by the indexing model from the issue text.

Description

Improvement

In https://github.com/open-telemetry/semantic-conventions/pull/342 they removed (client|server).socket.(address|port) in favour of network.(peer|local).(address|port).

They also didn't add this to any migration docs or changelogs anywhere 😓

There are also is net.sock.peer.port and net.sock.peer.addr which got deprecated accordingly. https://opentelemetry.io/docs/specs/semconv/attributes-registry/network/

Dominant language
TypeScript
Stars
16
Forks
6
Avg merge
2d 9h
Merged PRs (30d)
63

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/sentry-conventions

All issues in getsentry/sentry-conventions

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.