Closes: #17 Render Deployment Health Check Workflow#107
Merged
Conversation
p3ris0n
changed the title
Use `curl -s` (not `-sf`) so the actual response code is captured on 4xx/5xx, and fall back to 000 on connection failure — so the auto-filed incident issue reports the real status instead of 'failed'.
EmeditWeb
approved these changes
Jul 23, 2026
EmeditWeb
left a comment
EmeditWeb
left a comment
Member
There was a problem hiding this comment.
Clean ops improvement, suitable to merge. Scheduled (every 6h) + manual health ping of the existing /api/v1/health route; on non-200 it idempotently creates or comments on an incident-labeled issue (no spam), with least-privilege issues: write. README + progress-tracker updated; description matches the code; no duplicate workflow. I applied one small fix (commit 2c8ad92): switched curl -sf … || echo failed to curl -s … || echo 000 so the incident report captures the real HTTP status code instead of 'failed'. Approving and merging.
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.
feat: Add automated health check to prevent silent API outages
Description
This PR addresses the issue of the Render free-tier instance spinning down due to inactivity, which caused the first subsequent request to take 30+ seconds and allowed the service to experience silent outages without maintainers knowing.
A new GitHub Actions workflow acts as a heartbeat monitor. It pings the
/api/v1/healthendpoint every 6 hours to keep the instance warm. If the ping fails (returns a non-200 HTTP status), the workflow leveragesactions/github-scriptto automatically alert maintainers.To prevent issue spam during prolonged downtime, it implements a deduplication check: if an open
incidentissue already exists, it simply appends a comment to that issue rather than creating a new one.Changes Made
health-check.yml): Added a GitHub Action triggered via cron (0 */6 * * *) and manually viaworkflow_dispatch. Pings the live health endpoint and handles non-200 failures.github-scriptand the defaultGITHUB_TOKENto manage issues with theincidentlabel (no hard-coded secrets used).README.mdto document the heart-beat ping operation and theincidentlabel.context/progress-tracker.mdto log this architectural/ops change.Testing & Verification
scheduleandworkflow_dispatch.Related Issues
*Closes #17 *