feat(indexer): add request correlation ID generation#188
Merged
therealjhay merged 2 commits intoJun 30, 2026
Merged
Conversation
Contributor
|
kindly resolve conflict |
Contributor
Author
|
Conflict resolved |
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 pull request adds request correlation ID generation to the BettaPay indexer by configuring the Fastify server to use the shared
genReqIdutility from@bettapay/validation.Previously, the indexer did not explicitly generate standardized request correlation IDs, making it more difficult to trace requests across services and correlate logs during debugging. This implementation introduces the shared request ID generator directly into the Fastify constructor while preserving all existing server behavior.
Changes Made
genReqIdfrom@bettapay/validation.genReqIdto the Fastify constructor options.This solution follows the shared backend convention for request tracing while remaining fully backwards-compatible and requiring no API changes.
Fixes / Closes: #75
Type of Change
Verification & Test Plan
Automated Tests
pnpm build pnpm test pnpm lintManual Verification
request.id) generated bygenReqId.Sub-System Checklist
1. Smart Contracts (
BettaPay-Contract)cargo build --release --target wasm32-unknown-unknown)cargo test)auth.require_auth())2. Backend Services (
BettaPay-Backend)pnpm build).env.example3. Frontend Dashboard (
BettaPay-Frontend)pnpm build).env.localChecklist