Repository navigation
feat: monitor rate.vn home, health and public API - #5
Conversation
Adds three Upptime sites for rate.vn. /api/health now returns 503 when the Supabase read fails (DOS/Rate#829), so a database outage like the one on 2026-10-24 (DOS/Rate#814) opens a status issue. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
If your organization's extra usage balance is empty, an organization admin can add extra usage credits at claude.ai/admin-settings/usage. If its monthly spend limit was reached, an admin can raise it on the same page. If neither applies, contact Anthropic support.
Once extra usage is available, someone with write access to this repository can comment @claude review on this pull request to trigger a review.
|
No actionable comments were generated in the recent review.
 |
| Layer / File(s) | Summary |
|---|---|
Configure Rate.vn endpoint checks .upptimerc.yml |
Adds checks for the site root and API stats endpoint with 5,000 ms limits, and for the health endpoint with a 10,000 ms limit. A comment notes possible health-check 503 responses and cold starts of up to about 9 seconds. |
Priority:
Estimated code review effort: 2 (Simple) | ~8 minutes
Change: Feature
Merge Risk: 
23ed2
-
The three monitors and their response-time thresholds are ready to merge.
Pre-merge checks: 
-
Check name Status Explanation Description Check Check skipped - CodeRabbit’s high-level summary is enabled. Title check The title "feat: monitor rate.vn home, health and public API" matches the main change. The raw summary shows three Rate.vn uptime checks added to .upptimerc.yml: the site root, the health endpoint, an… Docstring Coverage No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0… Linked Issues check Check skipped because no linked issues were found for this pull request. Out of Scope Changes check Check skipped because no linked issues were found for this pull request. Full details: Title check
-
Explanation
The title "feat: monitor rate.vn home, health and public API" matches the main change. The raw summary shows three Rate.vn uptime checks added to .upptimerc.yml: the site root, the health endpoint, and the API stats endpoint. The objectives confirm the same three monitors. The title names the subject (rate.vn), the three monitored surfaces, and the change type (feat). It omits the response-time thresholds, which is acceptable because the title need not cover every detail.
Full details: Docstring Coverage
-
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
-
Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Comment @coderabbitai help to get the list of available commands.
![dos[bot]](https://avatars.githubusercontent.com/in/4711427?s=60&v=4){kind=small}
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request adds three new endpoints for Rate.vn to the Upptime configuration file. The review feedback suggests increasing the maxResponseTime threshold to 15000 ms for both the health and API endpoints to safely accommodate serverless cold starts and avoid false-positive downtime alerts.
| - name: Rate.vn Health | ||
| url: https://rate.vn/api/health | ||
| icon: https://rate.vn/img/rate-logo-64.png | ||
| maxResponseTime: 10000 |
There was a problem hiding this comment.
The comment on line 50 notes that cold starts can take up to ~9 seconds. Setting maxResponseTime to 10000 (10 seconds) leaves a very narrow margin of only 1 second. Under slight network jitter or platform load, cold starts can easily exceed 10 seconds, leading to false-positive downtime alerts. It is recommended to increase this threshold to 15000 (15 seconds) to provide a safe buffer and prevent alert fatigue.
maxResponseTime: 15000| - name: Rate.vn API | ||
| url: https://rate.vn/api/v1/rate/stats | ||
| icon: https://rate.vn/img/rate-logo-64.png | ||
| maxResponseTime: 5000 |
There was a problem hiding this comment.
Since the Rate.vn API endpoint (/api/v1/rate/stats) is also a serverless API route that queries the database, it will be subject to the same Vercel cold start delays (up to ~9 seconds) as the health endpoint. Setting maxResponseTime to 5000 (5 seconds) will highly likely trigger false-positive alerts on cold starts. It is recommended to increase this threshold to 15000 (15 seconds) to accommodate cold starts safely.
maxResponseTime: 15000
There was a problem hiding this comment.
Code Review
This pull request updates the .upptimerc.yml configuration file to add monitoring for three new endpoints: Rate.vn, Rate.vn Health, and Rate.vn API, specifying their URLs, icons, and maximum response times. There are no review comments, and I have no feedback to provide.
Adds three Upptime sites for rate.vn, which had no monitor:
/api/health, which reads Supabase and returns 503 when that read fails (ops(web): /api/health reports ok while the database is unreachable Rate#829, live since chore(release): promote dev to main (#829 and normalizer fixes) Rate#833). The threshold is 10 s because Vercel cold starts measured 4-8.5 s./api/v1/rate/stats, the public API, which needs the database. 5 s threshold.Why: on 2026-10-24 the Supabase legacy keys were disabled and rate.vn returned 500 for about 2 h 50 min with no alert (DOS/Rate#814).
All three URLs return 200 with user-agent
DOS, and so does the iconhttps://rate.vn/img/rate-logo-64.png.Approved by JOY in chat on 2026-10-24.
🤖 Generated with Claude Code
Summary by CodeRabbit