Skip to content

Request logs

Open User → Request Logs. This view lists real inference calls through the Proxy: timestamps, keys, users, models, route groups, status, and more — useful for troubleshooting and reconciliation.

OctaFuse Admin Request Logs page showing request status, users, models, routes, tokens, cost, and profit with emails and sensitive identifiers redacted.
Request Logs helps filter calls by time range, status, model, provider, protocol, and user. Emails and sensitive identifiers are pixelated in this screenshot.
  1. Open Request Logs.
  2. Narrow results with time range, status, model, user email, API key, vendor, route group, protocol, and other filters available on the page.
  3. Expand a row to inspect billing-audit snippets, request bodies, upstream bodies, and raw usage JSON (copy when provided).
  4. When reading money and timestamps, align with your system timezone and billing currency settings in Admin.

Expanded panels may include charge-related JSON summaries; for exact formulas or finance reconciliation, follow your internal policy plus upstream docs linked from the GitHub technical reference.

When a Route Pool has Provider Sticky enabled, expand route_trace.sticky in the request log:

  • lookup is the binding lookup outcome, such as hit, miss, expired, invalid_epoch, invalid_target, or invalid_circuit.
  • attempted_target is the bound Target tried before normal priority tiers.
  • result shows whether the binding was kept, cleared, created, or rebound; it can also report storage_error or unchanged.

Compare Sticky outcomes with cache-read tokens and upstream failover counts. If hits are stable but cache benefit does not improve, verify that the upstream really shares Prompt Cache state. Frequent cleared / rebound results point to Provider 429s, 5xx responses, auth failures, or an unsuitable TTL.

  • Audit logs — budget and account-side changes
  • Routing — four strategies and Provider Sticky
  • Simulator — browser-based calls to the Proxy with a real key