Routing Audit

Classification, decision, provider and actual-perimeter journal.

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

Open Routing Audit or Router requests in History.
Select a UTC window and tenant, then enter the request ID.
Expand the record and examine classification, policy rule, perimeter and upstream.
Save recurring filters as docs-investigation.
Export the selected window or load another page for older events.

Every control and its meaning

Control / parameter	Values, units and effect
Поиск / q	Search metadata and request IDs; full-text content search requires configured storage and permissions.
Фильтры / Filters	UTC time, tenant, action, perimeter, sensitivity, tier, model, injection, cache and error narrow results.
Сохранённый поиск / Saved search	Stores a named filter set. Removing a saved search does not remove audit records.
Настройки Secure / Content	Masking mode/floor and content capture belong to the gateway. Content TTL differs from metadata retention.

Verify the result

Verify ID, timestamp, blocking reason and content availability. A ring covers a limited history on one replica.

Errors, disabling and reverting changes

Reset filters for an empty selection. Restore failed PostgreSQL access instead of enabling unrestricted mode. Reload saved searches after permission changes.

**Routing Audit: persisted test-client request**
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. Filtered to the owned synthetic client; one persisted record was verified.

**Masking and protection floor settings · actual staging**
2026-10-15 · Actual staging application. Non-personal settings or aggregate test-stand metrics, not real customer statistics or a benchmark. Operator profile and other tenant lists excluded. Protection settings were not changed.

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