Extend Device Context with CPU info

[markushi]

Our device context docs describe a few new CPU related fields which are not provided by the mobile SDKs yet.

• processor_count
• cpu_description
• processor_frequency

Platforms

Beta Give feedback

1. Extend Device Context with CPU info sentry-java#2561
   Effort: Medium Effort: Small Platform: Android Platform: Java +4
   
2. Extend Device Context with CPU info sentry-cocoa#2740
   Effort: Small Impact: Medium Platform: Cocoa Status: Backlog +4
   
3. Extend Device Context with CPU info sentry-react-native#2884
   Platform: React-Native +1
   
4. Flutter (looks like protocol was updated here Update event contexts sentry-dart#838 but data isn't provided) -> follow up Use getExtraContext on iOS sentry-dart#1401

GH discussion on device classification getsentry/sentry#44422

[edwardgou-sentry]

Hey @markushi! I'm working on utilizing these fields in parallel, can I assume that processor_count will just be a simple number value and processor_frequency will be a number value representing frequency in mhz (ie 2500 for 2500mhz/2.5ghz)? This is also how this data is stored in profiles from what I can tell.

[kahest]

Hey @edwardgou-sentry! We want to adhere to the way of reporting these fields that exists from Profiling, so it's safe to assume this!

[edwardgou-sentry]

Awesome! Thanks @kahest ! 🙏

[brustolin]

It seems that for iOS there is no reliable way to retrieve CPU description or frequency.
The workarounds suggest to hard code the device model with such information, I think we should do this in the server side to avoid the need to update the SDK to include more information on every new device release.

We just need to compile an updated list like the one in this

[markushi]

@edwardgou-sentry before merging the Android PR, could you help me clarify the following:

1. do you know if the processor_count should be the number of logical cores or physical cores?
2. the processor_frequency is defined as a single number in the protocol, but can be different for every core - I assume we want to send over the highest value right?

[markushi]

@edwardgou-sentry any chance you could take a look into my questions above?

[edwardgou-sentry]

Hey @markushi , sorry I missed this!

1. This should be number of physical cores
2. Yes, we're looking for the highest performance core here

Thanks!