[Enhancement] Error monitoring uses console.error only — no Sentry or structured error tracking#1001
Open
Menjay7 wants to merge 1 commit into
Open
[Enhancement] Error monitoring uses console.error only — no Sentry or structured error tracking#1001Menjay7 wants to merge 1 commit into
Menjay7 wants to merge 1 commit into
Conversation
|
@Menjay7 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Contributor
|
Well done on the job done so far! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
Currently, error handling across the codebase relies solely on console.error. This approach makes debugging difficult in production environments, as errors are not captured in a centralized or structured way.
This PR introduces Sentry integration (or another structured error tracking solution) to improve visibility into runtime issues. It ensures that errors are logged both locally (for development) and remotely (for monitoring and alerting).
Changes
Added Sentry SDK initialization with environment-based configuration.
Replaced console.error calls with Sentry.captureException while retaining console output for local debugging.
Introduced a utility wrapper for error logging to standardize usage across the codebase.
Updated documentation to include setup instructions for Sentry DSN and environment variables.
Benefits
Centralized error tracking with stack traces and metadata.
Improved monitoring and alerting for production issues.
Easier debugging and faster resolution of user-facing errors.
Next Steps
Configure Sentry DSN in environment variables (.env).
Set up alerting rules in Sentry dashboard.
Audit existing error handling to ensure consistent usage of the new utility.
Closed #763