| Endpoint | Purpose | Expected response |
|---|
GET /api/v1/health | Liveness check for backend service | 200 with {"status":"OK"} |
GET / | Base API availability check | 200 with API metadata JSON |
- Health endpoint availability (
/api/v1/health success rate).
- API error rates (especially
5xx, 429, 401 spikes).
- Latency trends for core endpoints (
/urls/public, /auth/login, /urls/my-links).
- Backend process uptime and restart frequency (Koyeb instance events).
- Database connectivity and query failures (Prisma/PostgreSQL errors in logs).
| Metric | Warning | Critical |
|---|
| Health endpoint failure rate | > 1% over 5 min | > 5% over 5 min |
5xx error rate | > 1% over 5 min | > 3% over 5 min |
P95 latency (/urls/public) | > 700ms | > 1500ms |
| Koyeb instance restarts | >= 2 in 15 min | >= 5 in 15 min |
| DB connection failures | >= 1 recurring event | sustained failures > 2 min |
These thresholds are starting points for portfolio-scale traffic and can be tuned with real usage.
- Confirm backend is reachable:
GET https://api.korta.click/api/v1/health
- Check recent deploy and service status in Koyeb:
- Running / Healthy
- no route/path misconfiguration (
/ public route, /api/v1/health health path)
- Inspect backend logs:
- Prisma connection errors
- CORS/OAuth failures
- surge in
429 or 5xx
- Validate environment variables:
- DB, JWT, CORS, OAuth, SMTP
- If incident persists:
- rollback to last known good deploy
- rotate compromised secrets if relevant
- redeploy and verify
/api/v1/health + critical flows (shorten, login, OAuth).
