Health#862
Merged
Merged
Conversation
|
@Nanafancy is attempting to deploy a commit to the naijabuz's projects Team on Vercel. A member of the Team first needs to authorize it. |
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.
[BE-31] Add structured request logging middleware with correlation IDs in opsce module
Problem
The backend has no request logging. When errors occur in production, there is no way to trace a request through the system or correlate incoming requests with outgoing responses in logs.
Proposed Solution
Create backend/src/opsce/common/middleware/logger.middleware.ts. Generate a UUID correlationId per request, attach it to request and response headers, and log structured JSON per request/response.
Acceptance Criteria
Each request gets a X-Correlation-Id UUID header (generated if not provided by the client)
Logs incoming request: method, URL, correlationId, userAgent, IP
Logs outgoing response: statusCode, duration in ms, correlationId
Sensitive headers (Authorization, Cookie) are redacted from logs
Middleware applied globally in OpsceModule
Log output is structured JSON for log aggregation compatibility
closes #756