WHAT EACH METRIC MEASURES
The deployment’s Health tab shows these metrics for the Time window you choose.
Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Read a deployment’s traffic, errors, latency, and throughput, and act on what they show

| Metric | What it measures |
|---|---|
| Requests and Avg Requests / min | How much traffic the deployment served |
| Error Rate | The share of requests that failed. Hover to see the count. |
| Request Latency | The time from request to complete response, at the 50th, 95th, and 99th percentiles. It includes failed requests. |
| Time to First Token | The time until the first token of the response. For a non-streaming request, it equals the full latency. |
| Token Throughput | Input and output tokens per second |
| What you see | Likely cause | What to do |
|---|---|---|
| Errors rise | Cold starts, rate limits, or prompts that are too long | Open the failed requests on the Inference Logs tab and read their messages. See Errors. |
| Time to first token is high on some requests | Cold starts, or requests that wait for a busy replica | Set min replicas to 1 to avoid cold starts, or raise max replicas for concurrent traffic. See Autoscaling. |
| Latency is high, but time to first token is normal | Long responses | Lower max_tokens, or stream the response so users see it sooner. |
| Requests drop to zero | No traffic, or an application error before the request reaches Oumi | Check your application. With no traffic, quality monitoring has nothing to score. |
Was this page helpful?