Representing resources in Real User Monitoring

[ivomagi]

What are you trying to achieve?

Due to how browsers emit telemetry, the information about the environment resources (OS, IP, browser) can be captured from the existing protocol metadata (for example: IP of the browser, User-Agent HTTP header for OS and browser vendor/version), instead of including it in the payload. Converting this information to resources would be rather easy, but considering the information is already present in the metadata, it might just bloat the protocol with no real benefits. What would be the consensus here?

[ocelotl]

I asked Claude to review this issue and Claude suggests it be closed with this explanation:

Purely a semantic-conventions design question (labeled area:semantic-conventions) from May 2021 with zero comments, part of the RUM discussion #1679. Semantic conventions have since moved to open-telemetry/semantic-conventions, where browser resource conventions now exist (docs/resource/browser.md). This browser-resource question should be tracked there, not in the spec repo.

To guard against a mistaken suggestion, Claude then independently re-verified this conclusion:

Still OPEN, 0 comments, no closing PR/dup in timeline; open sem-conv design Q ("resource vs metadata") under RUM #1679 (also open). Sem-conv moved to semantic-conventions where docs/resource/browser.md exists, but that doc doesn't confirm this specific question was resolved — closeable as moved-repo, borderline stale-abandoned.

Claude evaluated this issue with medium confidence that it can be closed.

Claude has classified this issue as belonging in another repository.

The intention of this comment is to make it easier for a human being to review this issue before making a decision.

[svrnm]

Closing this, as this is now a semantic conventions issue, if this is incorrect, please open a new issue on the semantic conventions repository.