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
Currently, raygun4js wraps the console methods in order to create breadcrumbs from console messages. Unfortunately, this causes the console messages to show up as being logged from raygun.umd.js or equivalent bundle, which obscures the original source location from the users.
This can be worked around by blackboxing the Raygun source in the browser, or calling rg4js('disableAutoBreadcrumbsConsole'). However, this behaviour can still be very confusing.
We should disable this feature by default, and instead recommend rg4js('enableAutoBreadcrumbsConsole') to customers who want to opt-in to this feature. This should be less surprising, and should help ease our onboarding.
@Widdershin Hello, did I tell you that this error is proving to be blocking for our implementation since our clients cannot debug their applications? Are we thinking of changing provider of APM. Could you tell me how the progress of this issue is?
Currently,
raygun4js
wraps the console methods in order to create breadcrumbs from console messages. Unfortunately, this causes the console messages to show up as being logged fromraygun.umd.js
or equivalent bundle, which obscures the original source location from the users.This can be worked around by blackboxing the Raygun source in the browser, or calling
rg4js('disableAutoBreadcrumbsConsole')
. However, this behaviour can still be very confusing.We should disable this feature by default, and instead recommend
rg4js('enableAutoBreadcrumbsConsole')
to customers who want to opt-in to this feature. This should be less surprising, and should help ease our onboarding.Related: #348, #384
The text was updated successfully, but these errors were encountered: