Skip to content

Add device.manufacturer to semantic conventions for resources#2100

Merged
jsuereth merged 8 commits intoopen-telemetry:mainfrom
ladd:patch-1
Dec 16, 2021
Merged

Add device.manufacturer to semantic conventions for resources#2100
jsuereth merged 8 commits intoopen-telemetry:mainfrom
ladd:patch-1

Conversation

@ladd
Copy link
Copy Markdown

@ladd ladd commented Nov 4, 2021

Changes

  • Proposed manufacturer field

@ladd ladd requested review from a team November 4, 2021 21:00
@linux-foundation-easycla
Copy link
Copy Markdown

linux-foundation-easycla bot commented Nov 4, 2021

CLA Signed

The committers are authorized under a signed CLA.

@github-actions
Copy link
Copy Markdown

This PR was marked stale due to lack of activity. It will be closed in 7 days.

@github-actions github-actions bot added the Stale label Nov 16, 2021
@ladd
Copy link
Copy Markdown
Author

ladd commented Nov 16, 2021

Could I get a review, please?

@arminru arminru added area:semantic-conventions Related to semantic conventions spec:resource Related to the specification/resource directory labels Nov 16, 2021
@arminru arminru changed the title Update device.md Add device.manufacturer to semantic conventions for resources Nov 16, 2021
@arminru
Copy link
Copy Markdown
Member

arminru commented Nov 16, 2021

@ladd Please note that you will need to update the YAML definitions in this folder following the readme there:
https://github.com/open-telemetry/opentelemetry-specification/tree/main/semantic_conventions
By running the command documented there, the markdown table you edited manually will be generated automatically an make the build pass.

@ladd
Copy link
Copy Markdown
Author

ladd commented Nov 16, 2021

@ladd Please note that you will need to update the YAML definitions in this folder following the readme there: https://github.com/open-telemetry/opentelemetry-specification/tree/main/semantic_conventions By running the command documented there, the markdown table you edited manually will be generated automatically an make the build pass.

Thanks -- done!

@Oberon00
Copy link
Copy Markdown
Member

Is this something we'd actually want to send? Since we already send device IDs, couldn't this be handled with a device database at the backend? Or do you think the practical advantages will be enough? Does one usually have an API that the instrumentation could call to get the manufacturer? Or would it have to have a DB?

@ladd
Copy link
Copy Markdown
Author

ladd commented Nov 16, 2021

Device ids are typically not mappable to manufacturer strings, unless you have a separate instrumentation mechanism to populate a DB. Device model strings can sometimes be mapped, but it normally requires licensing a proprietary database (like GSM Arena) I do think the practical advantages are there -- specific Android manufacturers often tweak the OS in compatibility breaking ways. The API exists for Android -- see my footnote in the PR. For iOS, you would normally just hardcode Apple.

@github-actions github-actions bot removed the Stale label Nov 17, 2021
@github-actions
Copy link
Copy Markdown

This PR was marked stale due to lack of activity. It will be closed in 7 days.

@github-actions github-actions bot added the Stale label Nov 25, 2021
@ladd
Copy link
Copy Markdown
Author

ladd commented Nov 26, 2021

Can I get a review / merge if the comments have been addressed?

Copy link
Copy Markdown
Member

@Oberon00 Oberon00 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add a CHANGELOG entry.

@github-actions github-actions bot removed the Stale label Nov 27, 2021
@ladd
Copy link
Copy Markdown
Author

ladd commented Dec 6, 2021

Can I get a review / merge if the comments have been addressed?

@github-actions
Copy link
Copy Markdown

This PR was marked stale due to lack of activity. It will be closed in 7 days.

@github-actions github-actions bot added the Stale label Dec 14, 2021
@jsuereth jsuereth enabled auto-merge (squash) December 15, 2021 17:08
auto-merge was automatically disabled December 15, 2021 17:57

Head branch was pushed to by a user without write access

ladd added 2 commits December 15, 2021 13:31
Proposed manufacturer field
@jsuereth jsuereth enabled auto-merge (squash) December 16, 2021 00:21
@jsuereth jsuereth merged commit 86b4585 into open-telemetry:main Dec 16, 2021
carlosalberto pushed a commit to carlosalberto/opentelemetry-specification that referenced this pull request Oct 31, 2024
…-telemetry#2100)

* Update device.md

Proposed manufacturer field

* Update device.md

* Generate tables

* PR comments

* Remove trailing whitespace

* Update CHANGELOG.md

Make linter happy?

* Fix merge

Co-authored-by: Josh Suereth <joshuasuereth@google.com>
schmikei pushed a commit to schmikei/opentelemetry-specification that referenced this pull request Apr 17, 2025
…-telemetry#2100)

* Update device.md

Proposed manufacturer field

* Update device.md

* Generate tables

* PR comments

* Remove trailing whitespace

* Update CHANGELOG.md

Make linter happy?

* Fix merge

Co-authored-by: Josh Suereth <joshuasuereth@google.com>
schmikei pushed a commit to schmikei/opentelemetry-specification that referenced this pull request Apr 17, 2025
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:semantic-conventions Related to semantic conventions spec:resource Related to the specification/resource directory Stale

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants