You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all,
As I described above, I am using Angular6 + Ngrx6.
What I want to do is that sending an error to Sentry when webApp fails api call.
Let's say, I call an api called /abc/3 which does not exist.
Then client gets 404 Not Found error.
And this is the one that I want to send to Sentry through @sentry/browser.
Then I could catch the network error.
But the problem is I can't see any in my Sentry dashboard.
I checked my Chrome network tab. And I could find a message : "Non-Error exception captured with keys: error, headers, message, name, ok…"
So I guess @sentry/browser doesn't think this is an error.
I also found out this that talking about Non-Error exception captured with keys: error, headers, message, name, ok…
So here is my questions.
@sentry/browser is meant to be catching client network error?
If 1 is true, how can I make it work ? (Hopefully Angular way)
If 2 is false, should network error be handled by backend?
Thanks!
The text was updated successfully, but these errors were encountered:
Package + Version
@sentry/browser
@sentry/node
raven-js
raven-node
(raven for node)Version:
Description
Hi all,
As I described above, I am using Angular6 + Ngrx6.
What I want to do is that sending an error to Sentry when webApp fails api call.
Let's say, I call an api called
/abc/3
which does not exist.Then client gets
404 Not Found
error.And this is the one that I want to send to Sentry through
@sentry/browser
.I have created a simple service.
and have created
SentryErrorHandler
which extends Angular'sErrorHandler
This code detects well normal js error such as
abcdefg(); // <- this function doesn't exist so it occurs an error and sent to Sentry.
However, I figured out that the above code doesn't detect network error. ( Like I said
/abc/3
)So I have created
ErrorInterceptor
which extends Angular'sHttpInterceptor
.Then I could catch the network error.
But the problem is I can't see any in my Sentry dashboard.
I checked my Chrome network tab. And I could find a message :
"Non-Error exception captured with keys: error, headers, message, name, ok…"
So I guess @sentry/browser doesn't think this is an error.
I also found out this that talking about
Non-Error exception captured with keys: error, headers, message, name, ok…
So here is my questions.
Thanks!
The text was updated successfully, but these errors were encountered: