diff options
Diffstat (limited to 'doc/development/fe_guide/sentry.md')
| -rw-r--r-- | doc/development/fe_guide/sentry.md | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/development/fe_guide/sentry.md b/doc/development/fe_guide/sentry.md index 929de1499c7..95a170b7976 100644 --- a/doc/development/fe_guide/sentry.md +++ b/doc/development/fe_guide/sentry.md @@ -39,7 +39,7 @@ to our Sentry instance under the project The most common way to report errors to Sentry is to call `captureException(error)`, for example: ```javascript -import * as Sentry from '@sentry/browser'; +import * as Sentry from '~/sentry/sentry_browser_wrapper'; try { // Code that may fail in runtime @@ -53,6 +53,9 @@ about, or have no control over. For example, we shouldn't report validation erro out a form incorrectly. However, if that form submission fails because or a server error, this is an error we want Sentry to know about. +By default your local development instance does not have Sentry configured. Calls to Sentry are +stubbed and shown in the console with a `[Sentry stub]` prefix for debugging. + ### Unhandled/unknown errors Additionally, we capture unhandled errors automatically in all of our pages. |