feat: add /health endpoint for platform health checks#542
Open
xpoes123 wants to merge 1 commit into
Open
Conversation
xpoes123
changed the title
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
1 participant
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.
Adds a
/healthGET endpoint that returns HTTP 200 immediately, giving platform health checkers (Heroku, uptime monitors, load balancers) a fast, reliable signal that the process is alive.Problem
The server had no dedicated health route. Health checks from Heroku or other infrastructure would hit a full application route, which may perform database work or be gated behind heavier middleware. During DB reconnect delays or cold starts, those checks could fail or time out, causing unnecessary restarts.
Changes
router.get('/health', (req, res) => res.sendStatus(200))inroutes/index.js, registered before the heavier sub-routers so it responds as early as possible.Risk & testing
The route is a single line with no side effects and no database access. It cannot break any existing route because
/healthwas previously unhandled. Low risk;node --checkpasses.