Skip to main content

Developers: Live Traffic Metrics

Audience: Developers and support teams

The Live Traffic strip in Settings -> Developers -> System Key summarizes recent public API activity for the selected mode.

These metrics are operational diagnostics. They help you spot integration activity, errors, latency, throttling, and key availability quickly. They are not billing-grade usage records and should not be used as the only source for formal reporting.

Data Source And Refresh​

The dashboard reads recent request-log entries for the selected mode and system API key context when available.

  • The view refreshes automatically about every 15 seconds.
  • The sample is limited to recent request-log entries shown to the dashboard.
  • No sample or 0 usually means there is no recent matching request-log data.
  • Test and live modes are separated. Test-mode activity does not count as live-mode activity.

Requests Per Minute​

Requests / min is the number of matching public API requests observed during the last 60 seconds.

Use it to confirm whether an integration is currently sending traffic. A value of 0 means the dashboard did not find matching requests in the last minute.

Error Rate​

Error rate is the percentage of matching sampled requests that returned an HTTP status code of 400 or higher.

Common causes include:

  • invalid or expired credentials
  • mode mismatch between token and X-EshopOS-Mode
  • validation errors in request parameters
  • unavailable downstream services

Investigate high error rates in the Request Logs tab before rotating credentials.

P95 Latency​

p95 latency is the 95th percentile response time from the sampled request logs.

It answers: "How slow were the slowest 5 percent of sampled requests?" This is usually more useful than average latency because it shows tail latency that real integrations feel.

No sample means there were no matching latency samples available.

Throttled​

Throttled counts sampled requests that returned HTTP 429.

This usually means the integration is exceeding rate limits or retrying too aggressively. Add backoff, reduce polling frequency, or batch work where possible.

Active Keys​

Active keys is the number of active system API keys for the selected mode.

Keep this number low. Prefer one active key per environment unless you are rotating credentials or intentionally running separate backend systems.

How To Use These Metrics​

Use the strip as a quick operating check:

  • Requests / min confirms traffic is flowing.
  • Error rate confirms whether the integration is failing.
  • p95 latency shows whether responses are becoming slow.
  • Throttled shows whether rate limits are being hit.
  • Active keys shows how many system keys can currently call the API.

For investigation, open Request Logs and filter by mode, path, status, or key prefix.