Errors
Failed evaluation calls and errors reported by SDKs, with API response times.
What this page is for#
The Errors page shows how healthy the evaluation API is. It counts requests and failures and reports latency, and it includes errors your SDKs send in. It shows counts only, never who was evaluated.
In the console it lives at /errors. You see it in the sidebar when your role has metrics.read.
What you can do#
Set the scope
Pick a project, an environment and a time range.
Read the tiles
API requests, error rate, latency p95 and errors reported by SDKs.
Follow errors over time
A chart of errors for the evaluation API over the last 24 hours, 7 days or 30 days, with one column per day for the longer ranges.
Break errors down
Panels group them by error type, flag, SDK and environment.
Check endpoints
A table lists requests, errors and p95 latency per endpoint. Click a header to sort by endpoint, requests, errors or latency.
Good to know#
- Calls made with an API key are counted. With none, the page says Nothing recorded.
- SDK errors arrive through POST /api/v1/evaluation/errors, and the page explains the body to send.
- The By flag panel only includes errors that name a flag.
- The page needs metrics.read.