Files
BruscaiandCursor aa2eee41d4 Investigate Sora latency by plan (#1069 metrics) (#139)
## Summary
- Add Datadog metrics `artcraft.sora.enqueue` and
`artcraft.sora.job_duration_ms` tagged by `plan`, `model`, `resolution`,
`duration_s`, and `outcome` for `sora_2` / `sora_2_pro`.
- Cover omni-gen Fal enqueue plus legacy multi-function Sora handlers,
and Fal webhook success/failure completion.
- Document suggested Datadog queries in
`_docs/sora_latency_investigation_1069.md`.

**No behavior change.** Sora models remain `is_disabled`. Fix PR only
after admin reviews the metrics (artcraft
[#1069](https://github.com/storytold/artcraft/issues/1069)).

Companion desktop PR: opened against `storytold/artcraft` from the same
investigation branch.

## Test plan
- [ ] `SQLX_OFFLINE=true cargo test -p storyteller-web --bin
storyteller-web sora_latency_metrics`
- [ ] Deploy / soak; in Datadog compare p50/p90
`artcraft.sora.job_duration_ms` by `plan` + `model`
- [ ] Confirm enqueue counter increments only for Sora models
- [ ] Confirm no change to billing, Fal keys, or `is_disabled`

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-11-11 11:16:33 -05:00
..
2026-02-09 00:28:57 -05:00
2025-07-01 20:06:05 -04:00
2026-10-09 11:31:28 -04:00