Terminus#863
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. |
|
@Nanafancy 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! 🚀 |
yusuftomilola
approved these changes
Jun 1, 2026
Collaborator
yusuftomilola
left a comment
yusuftomilola
left a comment
There was a problem hiding this comment.
Thanks for your contribution
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
2 participants
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-30] Implement health check endpoints using @nestjs/terminus in opsce module
Problem
@nestjs/terminus is installed but never used. There is no way to verify the application's dependencies (database, Redis) are healthy, making deployment health checks and monitoring impossible.
Proposed Solution
Create backend/src/opsce/health/health.controller.ts using TerminusModule. Add indicators for PostgreSQL and Redis connectivity.
Acceptance Criteria
GET /api/health returns 200 OK with service statuses when all checks pass
Returns 503 Service Unavailable if any check fails
Checks PostgreSQL connectivity via TypeOrmHealthIndicator
Checks Redis connectivity via MicroserviceHealthIndicator or a custom indicator
Checks disk storage with a 90% threshold via DiskHealthIndicator
Endpoint is excluded from JWT auth (publicly accessible for load balancers)
closes #755