Feat: Add Sentry monitoring for runtime exception capture (#823)#884
Open
Delightech28 wants to merge 2 commits into
Open
Feat: Add Sentry monitoring for runtime exception capture (#823)#884Delightech28 wants to merge 2 commits into
Delightech28 wants to merge 2 commits into
Conversation
Contributor
|
@Delightech28 |
Contributor
|
@Delightech28 |
|
@Delightech28 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
|
Run cargo clippy --all-targets --all-features -- -D warnings |
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
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 integrates Sentry monitoring for runtime exception capture into the backend, addressing #823.
Changes Made
sentry,sentry-tracing, andsentry-towercrates.SENTRY_DSNfrom environment variables.main.rsbefore initializing telemetry to capture all early errors. The Sentry guard is maintained for the application's lifecycle to ensure asynchronous error reporting.sentry_tracing::layer()to the tracing subscriber intelemetry.rsto automatically captureerror!level events.sentry_tower::NewSentryLayerandsentry_tower::SentryHttpLayerto the Axum Router to automatically extract request contexts (client IP, HTTP headers, etc.).jwt_auth_middlewareandsignature_auth_middlewareinauth.rsto utilizesentry::configure_scope()for injecting the activeuser_idcontext.Acceptance Criteria Met
How to Test
SENTRY_DSNenvironment variable in your.envfile.tracing::error!log.closes #823