Requests Served

​

What it tells you

• Total request volume in the selected window.
• How that compares to the previous period.
• Hourly / daily distribution — peaks, troughs, anomalies.

​

How to read the chart

​

Pull via API

curl -sS "https://api.tenbyte.io/cdn/distributions/$DISTRIBUTION_ID/analytics/requests?from=2026-05-01T00:00:00Z&to=2026-05-09T00:00:00Z&granularity=hour" \
  -H "Authorization: Bearer $TENBYTE_API_TOKEN" | jq

{
  "total_requests": 45012345,
  "series": [
    {"ts": "2026-05-01T00:00:00Z", "requests": 1923456},
    {"ts": "2026-05-01T01:00:00Z", "requests": 1876543}
  ]
}

​

Requests vs traffic

​

Spot abuse

• Bot scraping — same small object hit thousands of times.
• Cache busting — random query strings forcing every request to be unique.
• Probing — 404 flood from a vulnerability scanner.

​

Operational tips

• Group by path. The top 10 paths by request count usually drive the bulk of origin traffic.
• Watch off-hours. Sustained traffic at 03:00 local is rarely human.
• Combine with cache-hit ratio. High request count + low HIT% = origin pain. Tune cache rules.
• Alert on rate change, not raw totals — easier to write portable thresholds.