The log center records admin actions, model calls, authentication events, orders, redemptions, conversation runtime events, moderation events, and system events. Use it to audit changes, check cost, and trace failures.

Where to find it#

Open Logs in the admin console. The tabs are:

Each tab supports search, filters, sorting, paging, and a detail sheet. Click any row to open the detail. Clean up logs at the top right permanently deletes historical data.

Operation audit#

Records who did what and when.

• Columns: ID, Actor, Action, Resource, IP, Time, Request ID.
• Search: user ID, action, resource, request ID, IP, or detail. A pure number is treated as an actor user ID.
• Filters: Resource, Action, and Time range.
• Sort: ID newest/oldest first, Created newest/oldest first.
• Detail blocks: Event (action, resource, resource ID, created at), Actor (user, user ID), Request (request ID, IP, user agent).

Resources include Users and accounts, Conversations, Projects, Messages, Files, Memory, System settings, and Logs. Actions include sign-in, message and conversation changes, sharing, file changes, memory changes, settings updates, and admin user actions such as create, update status, revoke sessions, reset password, reset two-factor auth, delete user, and log cleanup.

Model calls#

Records each model request with usage and billing.

• Columns: ID, Caller, Model, Usage, Billing, Balance after settlement, Latency, Time.
• Search: user ID, platform model, upstream model, upstream name, binding code, or protocol. A pure number is treated as a caller user ID.
• Filters: Billing mode (Free, Usage, Per call, Per second, Tiered), Model, and Time range.
• Sort: Call time newest/oldest first, Cost high to low, Tokens high to low, Latency high to low.
• Detail blocks: Call (caller, user ID, conversation ID, call time), Model route (platform model, upstream name, upstream model, binding code, protocol), Usage billing (billed cost, balance after settlement, total tokens, input, cache read, cache write, output, reasoning, call count, latency), plus Raw Usage JSON.

The Usage column shows input, output (with a reasoning breakdown on hover), cache read, and cache write. For video usage it shows input images and output seconds. The cost cell shows a tooltip with the unit-price formula for the billing mode, including tiered ranges, cache write multipliers, and time-of-day rates.

Auth security#

Records identity events such as sign-in, registration, refresh, verification, failure, and lockout.

• Columns: ID, User, Event, Result, Reason, IP, Time, Request ID.
• Search: user ID or event type. A pure number is treated as a user ID.
• Filter: Result — Success, Failed, or Blocked.
• Sort: Occurred newest/oldest first, ID newest/oldest first.
• Detail blocks: Event (event, result, reason, occurred at), User (user, user ID), Request (request ID, IP, user agent).

Order records#

Shows subscription and top-up payment orders.

• Columns: ID, User, Order no., Type, Provider, Status, Amount, Time.
• Search: user ID, order no., provider, status, or external payment ID. A pure number is treated as a user ID.
• Filters: Order type (Subscription, Top-up), Provider (Stripe, EPay), Status (Pending, Paid, Expired, Failed), Time range.
• Sort: Created newest/oldest first, Paid newest first, Amount high to low.
• Detail blocks: Order (order no., order type, provider, status, created at, paid at), User, Payment (paid amount / base amount, credited balance, interval x cycles, external payment ID, external checkout ID).

Redemptions#

Shows redemption code usage.

• Columns: ID, User, Code, Reward, Balance after redemption, Time.
• Search: redemption ref no., code hint, or note.
• Filters: Reward type (Balance, Subscription plan), Code ID, User ID, and Time range.
• Sort: Created newest/oldest first.
• Detail blocks: Redemption (ref no., redeemed at), User, Redemption code (code hint, code ID, note, code status), Reward (balance amount and balance before/after, or plan name, duration, and subscription ID).

You can open this tab directly from a redemption code with View redemptions; the code ID filter is preselected.

Conversation events#

Records the steps inside one chat run: model requests, tool calls, retrieval, and task state.

• Columns: selection checkbox, ID, User, Scope, Event, Status, Upstream, Tool, Run ID, Time.
• Search: user ID, run ID, event, stage, title, or tool name. A pure number is treated as a user ID.
• Filters: Scope (Trace block, Trace event, Tool call), Event type, Status (Streaming, Completed, Error), Time range.
• Sort: Created newest/oldest first, Latency high to low, Event sequence oldest first.
• Detail blocks: Conversation event (run ID, scope, event, status, stage, seq, created at), User (user, user ID, conversation ID, message ID), Model route, Tool (tool name, tool call ID, latency, title, summary, payload size), and JSON sections for event payload, tool input, tool output, and tool error.

Select runs and click Delete run traces to remove their trace events. You can select up to 100 runs at a time. This deletes trace events only; conversations, messages, attachments, calls, and billing records are preserved.

Moderation events#

Visible to superadmins only. Shows content moderation checks.

• Columns: Event ID, User, Result, Direction, Modality, Latency, Created, Actions.
• Search: exact event ID, user, result, or run ID.
• Filters: Result (Passed, Hit, Failed open), Direction (Input, Output), Modality (Text, Image), category, and time range.
• Detail: shows the event fields, the decrypted text, and any isolated images. A failed image load is reported per image.

System events#

Records platform diagnostics, warnings, and errors.

• Columns: ID, Level, Source, Event, Resource, Message, Request ID, Trace ID, Time.
• Search: source, event, resource, request ID, or detail.
• Filters: Level (Info, Warn, Error), Source, Event, and Time range. Source and event options are built from the events already loaded.
• Sort: Created newest/oldest first, ID newest/oldest first.
• Detail blocks: Event (level, source, event, message, created at), Resource (resource, resource ID), Request (request ID, trace ID).

Use this tab for file processing, vectorization, async tasks, external service connectivity, and runtime exceptions. Treat higher levels first.

Clean up logs#

1. Click Clean up logs.
2. Choose Log type: Operation audit, Auth security, Model calls, Order records, Conversation events, or System events.
3. Pick a Cutoff date. Data before that date at 00:00 is deleted; the selected date itself is not included.
4. Read the Impact note. Model calls and Order records are marked High risk.
5. Click Clean up.

This is permanent. Audit and auth cleanup only removes tracking records. Usage cleanup affects historical daily and monthly usage and current-cycle quota calculations. Order cleanup removes payment traceability and idempotency evidence. Conversation cleanup keeps conversations and messages but removes processing traces.

Detail JSON#

Most detail sheets include a Detail JSON section with a copy button. Conversation events split their JSON into payload, input, output, and error. Model calls include Raw Usage JSON from the upstream. Payloads above the safe viewing limit are not loaded and show a size note instead.

Treat detail JSON as internal. It can contain user, model, resource, order, and internal context data.

Troubleshooting#

Related#

• Billing for model pricing, orders, and redemption codes.
• Tools for MCP tool calls seen in conversation events.
• Content moderation for the policy behind moderation events.
• Accounts for the users referenced by these logs.