Missing known GPU details (max texture size, graphics shader level, support for ...)

[ShawnCZek]

Environment

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

Version

23.1.0

Link

No response

DSN

No response

Steps to Reproduce

1. Create a new exception event
2. 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
3. Send the event to a native project
4. 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/#gpu-context

Actual Result

This issue is similar to #42969. There are two differences between these two:

• Right now, the GPU values are somehow displayed in the administration
• However, these properties are not described in the types even when they are documented (as shown above):
  

  sentry/static/app/components/events/contexts/gpu/types.tsx

  Lines 1 to 11 in 623a055

  	export enum GPUKnownDataType {
  	ID = 'id',
  	NAME = 'name',
  	VERSION = 'version',
  	VENDOR_NAME = 'vendor_name',
  	VENDOR_ID = 'vendor_id',
  	MEMORY = 'memory',
  	NPOT_SUPPORT = 'npot_support',
  	MULTI_THREAD_RENDERING = 'multi_threaded_rendering',
  	API_TYPE = 'api_type',
  	}

The context then appears like this:

Therefore, I am not entirely sure whether these properties should be added to the administration or whether they should be removed from the documentation as they are/were deemed unofficial.

[getsantry]

Assigning to @getsentry/support for routing, due by Thursday, February 2nd at 10:56 (yyz). ⏲️

[getsantry]

Routing to @getsentry/open-source for triage, due by Friday, February 3rd at 5:00 pm (sea). ⏲️

[hubertdeng123]

Thanks for bringing this up, could you comment your problem in the previous issue you've opened?
#42969

It seems like a similar enough issue that potentially can be solved at one time and it'd be nice to avoid the switching between issues for context.

[ShawnCZek]

@hubertdeng123 Since this has slightly different behavior and affects a different context, I rather opened a different issue. However, if you maintain all contexts together, I can edit the original issue.

[ShawnCZek]

Per the request above, I have merged this issue with #42969.