Skip to content

ops: note the standing 503 from /api/pro-monitor (pro path itself healthy) #722

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
devswha merged 1 commit into from
Sep 4, 2026
Merged

ops: note the standing 503 from /api/pro-monitor (pro path itself healthy) #722

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/operations/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,6 +58,13 @@ live, which is terminal, and which must not be edited.
## Known open loops (recorded, not resolved here)

- First healthy `OBS-ALERT-v1` receipt after live-open: no record found.
Observed 2026-09-04 (08:31, 08:45, 09:00 KST, three consecutive production
deployments including the one before the key rotation): every 15-minute
`GET /api/pro-monitor` returns **503 `monitor_unavailable`**, while the
synthetic pro `POST /api/rewrite` it issues one second later returns 200.
The pro serving path is healthy; the monitor's aggregate/log adapters are
not. Pre-existing, not caused by the rotation; owner to inspect the
observability adapters (`PATINA_OBSERVABILITY_*`, `PATINA_VERCEL_LOG_QUERY_*`).
- Refund path for number-safety failures (`src/rewrite-handler.js` still says
"no refund path").
- Free-tier engine: resolved 2026-09-02 — owner confirmed gemini; no record
Expand Down