<no message value> entries in Sentry from raven.js
See original GitHub issueVersions:
raven.js 3.5.0
Sentry: 8.3.3
Exception Handler: AngularJS 1.5.8
Hi, I have one of the following in my AJS exception handler. This generates ‘no message value’ entries but more detailed content.
Raven.captureException(exception);
This, however, has a proper message header but much less detail in the content:
Raven.captureException(exception.stack);
For visual reference, I have the following generated in Sentry depending on when I pass ‘exception.stack’ vs ‘exception’ to Raven.captureException: Thoughts greatly appreciated.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:13 (5 by maintainers)
Top Results From Across the Web
Usage | Sentry Documentation
Raven will automatically catch and report any unhandled errors originating inside this function (or anything it calls, etc), so you don't have to...
Read more >raven-js Documentation
Raven.js is a tiny standalone JavaScript client for Sentry. ... Note: Without setting this, all messages will be rejected!
Read more >Integrated error tracking compatibility with Sentry SDK - GitLab
Just tested on an ember application (javascript), I got an error 500. Please find the sentry request. fetch("https://gitlab.com/api/v4/error_tracking/collector/ ...
Read more >How do I test that Sentry is reporting errors? - Stack Overflow
When execution is paused: in your console enter something like api = undefined and hit enter to update the state. Then continue execution...
Read more >Changelog - Docs - Sentry Documentation
Changed the grouping and default in_app values for cocoa events. ... like raven-js will now able to securely send messages to Sentry, without...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@vladgurovich – totally fair; we’ll try to better assess behavior changes as they correspond with Sentry server versions going forward.
@megabyzus @biggestT – okay, I totally missed this piece of information. You’re using older on-premise versions.
And yeah, this is the cause. In Sentry 8.6 we made some changes so that the
message
interface is no longer necessary. I should have noted this in my release notes for raven-js. An oversight on my part; I am developing against getsentry/sentry master almost 100% of the time.So, a couple ideas here:
I also recommend, if you are using on-premise Sentry, you should be pinning you raven-js versions explicitly.