Sever: Add Sentry #44
Merged
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
Previously, the server had basic console logging but no structured error tracking. When things went sideways in production, we were flying blind.
Now we have proper error monitoring with contextual information:
The streaming chat handler now captures errors with request context, making debugging production issues actually possible. Added proper graceful shutdown handling to ensure error data gets flushed before the process exits.
Also fixed the CI pipeline - it was missing
SENTRY_DSN
andJWT_SECRET
environment variables, which would cause Docker integration tests to fail silently. The kind of thing that makes you question your life choices at 2 AM.