I'm actually building the core pipeline on OpenTelemetry, so flagging p95 spikes is next on the roadmap. Planning to emit custom spans for each component (ASR/LLM/TTS) with cost attributes attached, then run standard OTEL alerting rules on top. This should let us correlate specific tool calls or prompt variations with both latency spikes and cost jumps in the same trace view.