Jev monitoring guide
Monitor your decision service and the door you call. Do not scrape a rival “is Jev down” page. TypeSafe’s own status/changelog — when they publish one — is the outbound authority; we will not impersonate it.
Independent operate notes — not TypeSafe’s status page and not a cloned “is Jev down” URL. Pinning how-to: version pinning. Canonical: docs.typesafe.ai. Replicas are not Jev and not endorsed.
Independent angle (cover, do not clone)
Win delta (status-and-changelog): pinning + alias policy; outbound official status/changelog; not a status-page clone.
What to page on
- Spike in 401 (key/door)
- 429/529 sustained beyond budget
- 422 spike (shipped bad questions)
- Sudden jump in review rate (alias move or bad deploy)
response.model≠ expected pin
What not to clone
A third-party uptime URL as if it were TypeSafe. Link official status if/when they document it (e.g. a status host they name). Until you verify a URL, use their docs, Discord, and HTTP errors.
If you find a TypeSafe-operated status page, add it to your runbook as outbound only. A hostname we have not verified in this batch is not printed here as fact.
Canary
A tiny Noul on a fixed sentence every minute tells you if the door is up. Alert on canary fail and on response.model drift. That is more honest than cloning a third-party “is Jev down” URL.
Changelog curiosity goes to TypeSafe SDK changelogs and models page, not a scrape of a rival handbook.
What the canary is not
A green toy Noul is not a quality signal. Pair the existing canary with:
- Alert if canary HTTP ≠ 200 (after bounded 429/529 retries — official SDK policy).
- Alert if
response.model≠ the pin you intended (jev-1.13.0vs whateverjev-latestresolved to). - Alert if canary tokens or latency explode — someone pointed the job at a dump-truck payload.
GET /v1/models is a cheap second probe. Interpret 401 (key/door) separately from 529/timeout (capacity). This site is not an oracle. Trace fields live on observability; pin policy on versioning.
Page / do-not-page
| Signal | Page? | Why |
|---|---|---|
| Canary fail + 401 | Yes (secrets) | Not a model outage |
| Sustained 429/529 beyond budget | Yes if no skip-smart-gate | Vendor limits can be dynamic |
| 422 spike | Yes (pack) | Revert SHA |
| Review-rate jump + model drift | Yes (pin) | Floors may be wrong |
| Single 529 | Usually no | Skip the smart gate |
| Vendor blog multiple moved | No | Not your KPI |
Do not scrape a rival “is Jev down” page. Do not mix SemIf/OpenJev canaries into the Jev board without a processor label.
When not to use this page’s advice
Do not treat jev.pro as TypeSafe status. Do not invent a changelog feed. Do not page humans because a replica host blinked. Schema-safe canary 200s do not prove production criteria are sane.
What this page does not claim
- Not TypeSafe’s status page.
- No invented changelog feed.
FAQ
Is Jev down?
Call GET /v1/models and a canary systemone with a tiny state. Interpret 401 vs 529 vs timeout. This site is not an oracle.
Should I pin in prod? Yes if floors exist. Aliases move.
Is a green canary enough to auto-act? No. It proves the door answered a toy Noul, not that floors still fit.
May I use a third-party uptime URL as official status? Not unless TypeSafe names that host. Link official docs until then.
Disclaimer
This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai. Never treat jev.pro as TypeSafe official documentation. We do not sell, issue, or proxy API keys.
Open-cluster pages are independent field-guide notes. Replicas and third-party interfaces mentioned anywhere on jev.pro are not Jev and not endorsed. Hub: Open. Siblings: versioning guide, observability guide, version pinning. Canonical: https://docs.typesafe.ai.