Add Sentry integration for error monitoring #32
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
|
Tested the Sentry integration by generating and monitoring test errors. Here is a screenshot from the Sentry dashboard, showcasing the captured errors. |
asacristani
force-pushed
the
feature/sentry-integration
branch
from
313305c to
2990c35
Compare
|
I have checked it too. It looks good to me. Thanks @MbxrAteeq ! |
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.
Description
This PR addresses the issue of integrating Sentry for comprehensive error monitoring and logging, as described in issue #18 The changes include setting up Sentry within the project to capture and track errors, providing improved visibility and real-time alerts for critical issues.
Changes Made
Testing Done
Related Issue
Resolves #18