User-Agent reduction, Client-Hints are not supported

[suzukieng]

Is there an existing issue for this?

• I have checked for existing issues https://.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/browser

SDK Version

7.9.2

Framework Version

No response

Link to Sentry event

No response

Reproduction Example/SDK Setup

Device/browser/OS information is not available due to "User-Agent reduction" (https://privacysandbox.google.com/blog/user-agent-reduction-android-model-and-version).

This is not a bug in Sentry's SDK, but there should be documentation on how to provide provide Client-Hints to Sentry's SDK and those Client-Hints would need to be parsed by Sentry's event ingestion.

Sentry SDK users would need to provide Client-Hints to Sentry's origin, e.g. by adding a meta tag.

<meta http-equiv="Accept-CH" content="Sec-CH-UA, Sec-CH-UA-Model, Sec-CH-UA-Mobile, Sec-CH-UA-Form-Factor, Sec-CH-UA-Platform, Sec-CH-UA-Platform-Version">
<meta http-equiv="Delegate-CH" content="Sec-CH-UA https://xxx.sentry.io; Sec-CH-UA-Model https://xxx.sentry.io; Sec-CH-UA-Mobile https://xxx.sentry.io; Sec-CH-UA-Form-Factor https://xxx.sentry.io; Sec-CH-UA-Platform https://xxx.sentry.io; Sec-CH-UA-Platform-Version https://xxx.sentry.io">

I am the author of a client-side JavaScript SDK that sends usage events and have a similar issue (my users not seeing detailed device/OS statistics), and provide documentation to them on how to enable Client-Hints (https://docs.strich.io/deployment-guide.html#user-agent-client-hints-optional).

Possibly related issue:
getsentry/sentry#50137

Steps to Reproduce

1. Send Sentry event with the JS SDK, using a common device like a Samsung Galaxy S21
2. Observe that the device model is 'K' in the received event

Expected Result

If the party deploying Sentry activates User-Agent Client-Hints for Sentry's origins (which would have to be documented), then the HTTP requests containing events sent to sentry would include these Client-Hints and more detailed information on the device/OS/browser could be obtained.

Actual Result

This is an event sent from a Samsung Galaxy S21 running Android 15.

[andreiborza]

Hi @suzukieng, thanks so much for filing this and providing all this extra info on how you got around it in your SDK. We'll add this to our documentation too.

[suzukieng]

@andreiborza You're welcome! Are you saying that Sentry already processes Client-Hints, if they are delegated? Then we'd just need to know where to send them?

[andreiborza]

Yea, they're supported: https://.com/getsentry/relay/blob/0210399ae37694e8c2d50e6dd3fa07e860f3c6f5/relay-event-normalization/src/normalize/user_agent.rs#L199

[suzukieng]

Yea, they're supported: https://.com/getsentry/relay/blob/0210399ae37694e8c2d50e6dd3fa07e860f3c6f5/relay-event-normalization/src/normalize/user_agent.rs#L199

Ok, but where do I delegate them to? If I add https://sentry.io to the hints listed in the Delegate-CH meta tag, they don't seem to be sent. The requests are going to o.ingest.sentry.io