feat: add Sentry error tracking #165
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We need to track down some persistent errors in the app, and should have better visibility in general into web client performance - this will help with both. Staging/prod configuration are included in the build script here, and I've configured separate projects for dev/staging/prod in Sentry.
the latest versions of the sentry next.js plugin seem to have a bug that breaks next-on-pages: cloudflare/next-on-pages#891 pin to fix
Website preview 🔗✨ |
fforbeck
approved these changes
Dec 16, 2024
travis
pushed a commit
that referenced
this pull request
Dec 18, 2024
🤖 I have created a release *beep* *boop* --- ## [1.17.0](w3console-v1.16.2...w3console-v1.17.0) (2024-12-18) ### Features * add Sentry error tracking ([#165](#165)) ([3e7069a](3e7069a)) ### Bug Fixes * use the same Sentry project for different envs ([#167](#167)) ([32dd6f8](32dd6f8)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
fforbeck
pushed a commit
to storacha/upload-service
that referenced
this pull request
Feb 5, 2025
🤖 I have created a release *beep* *boop* --- ## [1.17.0](storacha/console@w3console-v1.16.2...w3console-v1.17.0) (2024-12-18) ### Features * add Sentry error tracking ([#165](storacha/console#165)) ([3e7069a](storacha/console@3e7069a)) ### Bug Fixes * use the same Sentry project for different envs ([#167](storacha/console#167)) ([32dd6f8](storacha/console@32dd6f8)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We need to track down some persistent errors in the app, and should have better visibility in general into web client performance - this will help with both.
Staging/prod configuration are included in the build script here, and I've configured separate projects for dev/staging/prod in Sentry.
Much of this was autogenerated by the Sentry Next.js setup wizard.