Analytics & usage

bytetourist records every request as an event and aggregates it for usage, billing, and dashboards — without slowing the proxy down.

Off the hot path

The proxy stays fast: after each response, the request is recorded asynchronously, so measurement never sits between you and your data. The raw event log is the immutable source of truth for billing; the dashboards read from aggregated rollups built on top of it.

What’s recorded per request

Each event carries: timestamp, org id, request id, node id and node IP, target host, method, URL, status code, latency (measured at the node), bytes in/out, region, country, and any error. Events are retained for 90 days.

Usage & billing rollups

Events are aggregated per org per hour, then rolled up into per-cycle usage for billing. Because the raw event log is immutable, usage is auditable and re-computable.

What you can see

In the dashboard:

Today — request count, success rate, credits used, active keys.
Credits vs. plan — credits spent against your monthly allotment, with what remains and % utilisation.
Recent requests — a paginated, org-scoped log with status, latency, and target host.
Trends — success/error-rate time series.

Fleet health

Node health and in-flight counts are measured continuously and fed back into routing, so lowest_latency routing and the circuit breaker act on fresh per-node data, and the fleet makes autoscaling decisions on the same signal.