ReportingObserver events get logged while the integration is not enabled

[davidsandoz]

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/vue

SDK Version

6.19.7

Framework Version

Nuxt.js 2.15.8 / Vue 2.6.14

Link to Sentry event

https://sentry.io/organizations/nothing-inc-02/issues/3398420478/?project=5570289&query=is%3Aunresolved+timesSeen%3A%3E10&sort=date&statsPeriod=14d

Steps to Reproduce

I have a Nuxt.js frontend which uses @nuxtjs/sentry, @sentry/tracing and @sentry/vue.

Sentry is configured in the nuxt.config.ts file:

  sentry: {
    dsn: 'https://[masked].ingest.sentry.io/[masked]',
    config: {
      release: '[app-name]@' + pkg.version
    }
  }

Events get properly logged, but since a few days ago we are getting a large amount of the following event: ReportingObserver [deprecation]: Deprecation messages are stored in the devtools-frontend repo at front_end/models/issues_manager/DeprecationIssue.ts.. It is our problem to deal with the event as such. However, as I looked into it, I found out that ReportingObserver events are not supposed to be tracked by default and are only opt-in with the ReportingObserver pluggable integration.

It's using @nuxtjs/sentry v5.1.7 and there's now v6.0.0, but it doesn't change the dependencies to the SDK version, which is still v6. I cannot use v7 because @nuxtjs/sentry doesn't support it yet (nuxt-community/sentry-module#433).

Apologies for still ticking the “I am using the latest SDK release”. Please just let me know if it's a known issue fixed in the latest release (I couldn't find anything about that). I would have rather asked a question than report a bug, but in the issue creation process, the link to “Ask a question” brings back to the issues list 😕

Expected Result

To not see any ReportingObserver events in Sentry when the pluggable integration is not enabled.

Actual Result

ReportingObserver events get logged in Sentry. (filled up my quota in 5 days)

[AbhiPrasad]

It seems that as per the sentry module docs, ReportingObserver is enabled by default. I would recommend passing config to disable this.

{
  ReportingObserver: false
}

ref:
https://github.com/nuxt-community/sentry-module/blob/db5bb9bb13d78af8146727a56a8bfd190b4cc24d/lib/core/options.js#L5
https://github.com/nuxt-community/sentry-module/blob/db5bb9bb13d78af8146727a56a8bfd190b4cc24d/lib/plugin.client.js#L6-L8

[davidsandoz]

Hmm, when I saw ReportingObserver: {} and that they mention it is supported, I didn't understand that it is enabled by default. But now seeing the example to “disable integration that is enabled by default” with ExtraErrorData that is set the same way as ReportingObserver, I can see now that it appears to be enabled by the Nuxt.js Sentry module.

Thank you for pointing this out. I'll try it out.

[davidsandoz]

It will take some time until I can confirm it helped. So, I'll close the issue, as the suggested solution is quite promising. If it doesn't work, I'll reopen.

[AnthonyRuelle]

Hi,

unable for me to remove these errors despite disabling in nuxt.config.ts
What did I do wrong?

[AbhiPrasad]

@AnthonyRuelle I would recommend reaching out to the Nuxt Sentry SDK folks to figure out why this is happening.

[ferdinandfrank]

Hi,

unable for me to remove these errors despite disabling in nuxt.config.ts What did I do wrong?

@AnthonyRuelle You have to wrap the ReportingObserver config into the clientIntegrations prop according to the docs:

sentry: {
   clientIntegrations: {
      ReportingObserver: false
   }
}

[Sweater-Baron]

To anyone who made it to this page: You actually probably don't want to disable the ReportingObserver integration. Leaving it enabled gives you insight into some browser/device-specific issues on your users' devices that you otherwise would not be able to observe.

The specific error message that the OP in this issue is complaining about seems to be a bug in either Sentry or Chromium and not supposed to be logged. I have filed an issue about that here: #5932