ReportingObserver integration frequently reporting a weird message that's not actually an issue

[Sweater-Baron]

Is there an existing issue for this?

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

How do you use Sentry?

Sentry Saas (sentry.io)

Which package are you using?

@sentry/react

SDK Version

7.15.0

Framework Version

7.15.0

Link to Sentry event

https://sentry.io/organizations/carver-edison/issues/3645089890/?environment=prod&project=6751029&query=is%3Aunresolved

Steps to Reproduce

Sentry is logging a weird non-error message as an issue via the ReportingObserver: "ReportingObserver [deprecation]: Deprecation messages are stored in the devtools-frontend repo at front_end/models/issues_manager/DeprecationIssue.ts."

This message appears to come from the Chromium source code here: https://chromium.googlesource.com/chromium/src/+/276b4b0cf6b2edcf6a397c43c53a30943ca173cf/third_party/blink/renderer/core/frame/deprecation/deprecation.cc#260

I'm unsure of whether this is an issue caused by Sentry calling the wrong ReportingObserver API, or if it's a Chromium bug, but:

1. Someone from Sentry will have to confirm this is not caused by incorrect behavior in Sentry's code, and if they find that it's a Chromium bug, they'll already have the context to file a bug report with Chromium, and should do so.
2. Even if it's a Chromium bug, Sentry should IMO add a workaround to stop this non-issue from being logged, because otherwise it's going to confuse people and take up a lot of people's error quota. It also seems to be leading people to (unwisely IMO) disable the ReportingObserver integration in Sentry completely: ReportingObserver events get logged while the integration is not enabled #5751

Expected Result

This does not get logged as an issue in Sentry, or if it is logged, does not count against quota.

Actual Result

Useless thing gets logged and is annoying

[AbhiPrasad]

We get the reports from the ReportingObserver and directly send them to Sentry.

sentry-javascript/packages/integrations/src/reportingobserver.ts

Lines 79 to 82 in 9056516

	const observer = new (getGlobalObject<any>().ReportingObserver)(this.handler.bind(this), {
	buffered: true,
	types: this._options.types,
	});

Users can filter these errors through beforeSend, by trying to detect ReportingObserver errors of this type and applying the rules accordingly:

sentry-javascript/packages/integrations/src/reportingobserver.ts

Line 126 in 9056516

hub.captureMessage(`${label}: ${details}`);

. I don't think we'll be adding a default here.

As for the chromium issue, we should investigate this! I will open up a ticket with chromium and see what's going on.

[AbhiPrasad]

Filed the chromium issue here: https://bugs.chromium.org/p/chromium/issues/detail?id=1373814