-
Notifications
You must be signed in to change notification settings - Fork 896
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
Add device.manufacturer
to semantic conventions for resources
#2100
Conversation
|
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
Could I get a review, please? |
device.manufacturer
to semantic conventions for resources
@ladd Please note that you will need to update the YAML definitions in this folder following the readme there: |
Thanks -- done! |
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? |
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 |
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
Can I get a review / merge if the comments have been addressed? |
There was a problem hiding this 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.
Can I get a review / merge if the comments have been addressed? |
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
Head branch was pushed to by a user without write access
Proposed manufacturer field
Make linter happy?
…-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>
Changes