Nice — those two features tend to unlock the “why” behind drift. One thing we found especially useful was pairing cost/outcome alerts with a root-cause slice: when slope jumps, immediately show top contributing endpoint/feature + tenant/user + prompt version changes + retry ratio/context size trend.
For your event_id model: how do you handle partial outcomes (e.g., success after fallback/escalation) and do you keep pricing snapshots by timestamp so historical cost/outcome comparisons stay consistent across model price changes?
No comments yet.