Skip to content

feat: Backend Error Monitoring and Sentry Integration#230

Merged
Cedarich merged 1 commit intoPulsefy:mainfrom
walterthesmart:feat/sentry-integration
Mar 29, 2026
Merged

feat: Backend Error Monitoring and Sentry Integration#230
Cedarich merged 1 commit intoPulsefy:mainfrom
walterthesmart:feat/sentry-integration

Conversation

@walterthesmart
Copy link
Copy Markdown
Contributor

@walterthesmart walterthesmart commented Mar 29, 2026

This PR resolves issue #228 by integrating comprehensive Sentry error tracking and standardizing the structured logging setup for backend services.

###Tasks Addressed

  • Sentry Integration: Configured @sentry/node and @sentry/profiling-node to capture errors, profile applications, and catch failures.
  • Request Context Redaction: Configured Sentry to meticulously report the application context, but heavily redacts all sensitive fields like passwords, secrets, and auth tokens.
  • Structured Error Logging: Upgraded LoggingInterceptor to track full error context alongside duration metrics.
  • Breadcrumbs and Context Validation: SentryService is introduced for tagging, user tracing, and custom breadcrumbs throughout the codebase to ensure robust traces.
  • Custom Exceptions Filter: SentryExceptionFilter is added to safely track internal 5xx errors while filtering out noise from 4xx (client mistakes).
  • Environment Updates: Sentry configuration logic validates using Joi and variables are documented in .env.example.
  • CI/CD Commands: Lint checks run successfully along with tests in the CI to guarantee the latest pushes don't break existing workflows.
    Closes Error Monitoring & Sentry Integration #228

Resolves Pulsefy#228

Tasks implemented:
- Integrated Sentry using @sentry/nestjs and @sentry/profiling-node.
- Created SentryModule and SentryService for injecting sentry capturing behaviors across the app.
- Configured a SentryExceptionFilter to intercept all unhandled internal server exceptions (status code 5xx) with fully sanitized request context (redacting secrets, tokens, and authorization fields).
- Standardized error logging in LoggingInterceptor to include full request context (correlation ID, parsed body without sensitive data).
- Verified linting, unit tests, and production build runs successfully in the workspace.
@drips-wave
Copy link
Copy Markdown

drips-wave bot commented Mar 29, 2026

@walterthesmart 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! 🚀

Learn more about application limits

@Cedarich Cedarich merged commit 7b6e5a3 into Pulsefy:main Mar 29, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Error Monitoring & Sentry Integration

2 participants