getsentry / getsentry/sentry

Missing known device/GPU details (processor, unique ID, support for ...)

Open
#42,969 11 comments 0 reactions 0 assignees View on GitHub
Bug Waiting for: Product Owner
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
1d 5h
Merged PRs (30d)
624

Description

### Environment

self-hosted ([https://develop.sentry.dev/self-hosted/]())

### Version

22.12.0

### Link

*No response*

### DSN

*No response*

### Steps to Reproduce

1. Create a new exception event
2. Add a device context and include one or more of the following keys:
* `device_unique_identifier`
* `processor_count`
* `processor_frequency`
* `supports_accelerometer`
* `supports_audio`
* `supports_gyroscope`
* `supports_location_service`
* `supports_vibration`
3. Add a GPU context and include one or more of the following keys:
* `max_texture_size`
* `graphics_shader_level`
* `supports_draw_call_instancing`
* `supports_ray_tracing`
* `supports_compute_shaders`
* `supports_geometry_shaders`
4. Send the event to a native project
5. View the event in issues

### Expected Result

Values of the mentioned keys will be appropriately formatted or at least visible as they are described in the documentation: [https://develop.sentry.dev/sdk/event-payloads/contexts/#device-context]()

### Actual Result

Right now, the values for the device context are not even displayed in the administration, supposedly due to how unknown keys are handled:
[https://github.com/getsentry/sentry/blob/664e9c80f6ec84fc0529134500b82c4a350c0dbc/static/app/components/events/contexts/device/getDeviceKnownDataDetails.tsx#L222-L223]()

This is what it looks like in the administration:

![Viewed device context in the event view](https://uploads.linear.app/3ed206af-f87a-40aa-82a0-150bf83e43e6/0f9dd976-db6c-4cc5-a835-77b8c26537f0/706836de-ee2a-419e-913f-630e4533ffbd?signature=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJwYXRoIjoiLzNlZDIwNmFmLWY4N2EtNDBhYS04MmEwLTE1MGJmODNlNDNlNi8wZjlkZDk3Ni1kYjZjLTRjYzUtYTgzNS03N2I4YzI2NTM3ZjAvNzA2ODM2ZGUtZWUyYS00MTllLTkxM2YtNjMwZTQ1MzNmZmJkIiwiaWF0IjoxNzg2NzQwMTY3LCJleHAiOjE4MTgzMTA3Mjd9.qXS5hL2XXTT-4Kz59paEQDh4_BK43Ijh4PNkY4UKlhY)

And this is the JSON of the device context from the event:

![Event JSON](https://uploads.linear.app/3ed206af-f87a-40aa-82a0-150bf83e43e6/fbb8c651-f311-4621-b05b-cf6d08d6c20c/272d86ff-f2be-4a82-bc94-c1d4b459d018?signature=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJwYXRoIjoiLzNlZDIwNmFmLWY4N2EtNDBhYS04MmEwLTE1MGJmODNlNDNlNi9mYmI4YzY1MS1mMzExLTQ2MjEtYjA1Yi1jZjZkMDhkNmMyMGMvMjcyZDg2ZmYtZjJiZS00YTgyLWJjOTQtYzFkNGI0NTlkMDE4IiwiaWF0IjoxNzg2NzQwMTY3LCJleHAiOjE4MTgzMTA3Mjd9.e79IDPhrDKW3XhND56A0bb4Zs4jzqYPDSa42Lxjs9XM)

On the other hand, the mentioned keys of the GPU context are shown in the administration. They are just not properly formatted:

![Wrongly formatted GPU context](https://uploads.linear.app/3ed206af-f87a-40aa-82a0-150bf83e43e6/d2030c73-e5da-4bff-a62a-55385dc4a6ce/9c49d998-1cdd-44bb-9097-e9aa3260a717?signature=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJwYXRoIjoiLzNlZDIwNmFmLWY4N2EtNDBhYS04MmEwLTE1MGJmODNlNDNlNi9kMjAzMGM3My1lNWRhLTRiZmYtYTYyYS01NTM4NWRjNGE2Y2UvOWM0OWQ5OTgtMWNkZC00NGJiLTkwOTctZTlhYTMyNjBhNzE3IiwiaWF0IjoxNzg2NzQwMTY3LCJleHAiOjE4MTgzMTA3Mjd9.nv7xLLaxvYJJi1UPjqq5dOzwEG7w0wvhb3mBZ4iV2yY)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.