Missing known device/GPU details (processor, unique ID, support for ...)
- 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:

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

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

Contributor guide
Assessment
This issue has not been assessed yet.