Sampling
Measuring every single request of a very busy app is not practical. When traffic is high, the edge keeps a statistically representative sample and scales the figures up:- Totals and percentiles are estimates. They are reliable for trends and comparisons, and they can differ by a small margin from an exact count.
- The Requests table shows a sample of the requests, not all of them. A specific request may not be in it.
- A sampled notice appears in the panel whenever this is happening. Apps with low or moderate traffic usually see exact data.
Delay
Data refreshes about every 5 minutes, so it can take a few minutes for a request to show up. The 5-minute and 15-minute shortcuts remain, with a notice about this delay. So:- The most recent minutes of a chart can still grow when you refresh.
- A request you just made may take a few minutes to appear in Requests.
- Use the Request ID and the time shown to match a row, rather than waiting for it to show up at the top.
When the panel is busy
Analytics has limits so that everyone gets a fair share:- Too many queries in a row. Many consecutive queries from the same account can return
429 RATE_LIMIT_EXCEEDED.details.retry_aftersays how many seconds to wait. - High-demand moments. When demand is very high and no recent result is available for the period, the answer is
503 ANALYTICS_BUSY, also withdetails.retry_after. The panel shows a countdown and tries again by itself.