Skip to content

Comments

Sentry Error Monitoring Integration #64

Merged
JerryIdoko merged 4 commits intoVesting-Vault:mainfrom
Adedayo-Data:main
Feb 23, 2026
Merged

Sentry Error Monitoring Integration #64
JerryIdoko merged 4 commits intoVesting-Vault:mainfrom
Adedayo-Data:main

Conversation

@Adedayo-Data
Copy link
Contributor

@Adedayo-Data Adedayo-Data commented Feb 23, 2026

Closes #47


Overview

This PR integrates Sentry (@sentry/node and @sentry/profiling-node) into the Vesting Vault backend to provide production-grade error monitoring and performance profiling. It specifically addresses the issue of silent crashes within the indexing service.

Changes Made Includes:

1. Core Integration: Initialized Sentry in index.js with environment-based configuration (Production vs. Staging tags).

2. Enhanced Error Context:

    - Wrapped processClaim to capture exceptions with full claimData (transaction hashes, token addresses, etc.) for easier debugging.

    - Integrated Sentry into processBatchClaims to ensure individual transaction failures are reported even if the batch continues.

    - Added instrumentation to processTopUpEvent, processReleaseEvent, backfillMissingPrices, and getRealizedGains.

3. Resilience: Updated catch blocks to prevent silent failures, ensuring stack traces are preserved and reported.

How to Test

- Set SENTRY_DSN in your .env file.

- Run the application and trigger a malformed claim via the /api/claims endpoint.

- Verify that the error appears in your Sentry dashboard with the associated transaction metadata.

@JerryIdoko JerryIdoko merged commit 7c60bb3 into Vesting-Vault:main Feb 23, 2026
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.

#28 Issue 28: [Ops] Implement Sentry for Error Monitoring

2 participants