Jev observability guide
Observability for Jev is decision traces, not pretty flame graphs of their GPU. If you cannot answer “which question SHA labeled this ticket?”, you are flying blind.
Unofficial. docs.typesafe.ai. No keys.
Minimum fields
request_id (yours), response.model, usage.input_tokens, question pack SHA, full probabilities, chosen action, door name, latency, HTTP status.
Metrics that matter
Auto vs review vs error rates; 429/529 counts; distribution of confidence; token p95 (cost + context). Do not chart a fake 193×.
Dashboards that lie
A single “AI accuracy” tile that averages Nouls with Choice confidences is meaningless (official: do not carry thresholds across types). Split panels by question id.
Do not import TypeSafe launch-post multiples into Grafana. If leadership wants a speed story, link the vendor post and show your p95 next to it.
What this page does not claim
- Not Datadog setup.
FAQ
Does TypeSafe send traces to us? You log the API response. We do not host your telemetry.
OpenTelemetry? Wrap your client. There is no official “Jev APM” in the public docs we used.
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: monitoring guide, glossary decision trace, api response schema. Canonical: https://docs.typesafe.ai.
Sources
Public TypeSafe or adjacent documentation only. No private claims.