Dashboard

Request activity, worker clients and routing overview.

Request activity, worker clients and routing overview.

This screen belongs to the Router deployment operator, not an ordinary hosted customer. Hosted customers have a separate account page with their own keys and limits; policy and service settings are not exposed there. Contact the operator to change protection. In the operator console, open the route listed above; a report tenant filter does not automatically scope a global setting.

Examples use educational data. Use your own authorized tenant in real integrations. Each screenshot shows the actual frontend, with the source and educational/demo mode stated below it.

Step-by-step actions

  1. Select the tenant in the top bar, then open Dashboard.
  2. Click Refresh Dashboard and check counter scope and history source.
  3. Select 30 s for monitoring; return to Off for a one-time review.
  4. When blocks appear, open Request history and locate the corresponding decision.

Every control and its meaning

Control / parameterValues, units and effect
TenantSwitch tenant selects authorized history; All tenants stays within the operator’s permissions.
Автообновление / Auto-refreshOff, 10, 30 or 60 seconds. Off stops the display timer; requests continue to be processed.
Запросы / RequestsTotal requests, routed, route errors and blocks are separate counters. Worker jobs are displayed separately.
Токены / TokensInput/Output reflect recorded usage. A record without usage does not prove zero cost; source defines history coverage.

Verify the result

Compare requests and recorded tokens with history for the same tenant. Router overhead excludes model generation.

Errors, disabling and reverting changes

On a source error, do not substitute worker counters for Router traffic. Restore history access and refresh.

Dashboard: test-client metrics
Dashboard: test-client metrics
2026-10-15 · Actual staging application. Synthetic client, public definitions or aggregate test-stand metrics only; not customer statistics or a benchmark. Original pixels are unmodified; personal profile and private data excluded.
  1. Requests and routing
  2. Tokens and latency

Detailed security settings · Traffic analysis · FAQ · All application sections