A "net::ERR_NAME_NOT_RESOLVED" error is not reported in Sentry

• Review the documentation: https://docs.sentry.io/
• Search for existing issues: https://github.com/getsentry/sentry-javascript/issues
• Use the latest release: https://github.com/getsentry/sentry-javascript/releases
• Provide a link to the affected event from your Sentry account

Package + Version

• @sentry/browser
• @sentry/node
• raven-js
• raven-node (raven for node)
• other:

Version:

5.13.0

Description

I am initializing Sentry like this:

Sentry.init({
  dsn: <my sentry dsn>
});

And then in my code I force an error like this:

function reqListener () {
   console.log(this.responseText);
}
let oReq = new XMLHttpRequest();
oReq.addEventListener("load", reqListener);
oReq.open("GET", "http://whiizzleee.commm/hahahahaha");
oReq.send();

This results in a “net::ERR_NAME_NOT_RESOLVED” error. I can see the error in the console, but Sentry is not reporting it.

I can see in the dev console, that the error is thrown at return originalSend.apply(this, args); in the trycatch.ts of sentry. Also in the network tab I do not see a request being sent to Sentry.

[ghost23]

I understand. OK, thank you for the explanations.

[kamilogorek]

Hmm, but isn’t the second example only caught, because of manually throwing the Error?

Yes, if code fails in any way there, eg. accessing null.foo it’d also catch it. The reason for wrapping vs. allowing it to bubble is that this way we have an access to the handler itself, it’s name, it’s event object etc. And not only error.

couldn’t you add yourself as a listener to the error and do a captureEvent by default?

We could, but in most cases it’d be simply way too noisy.