Skip to main content

Costs, logs & history

Dashboard​

Personal → Dashboard summarizes prompt usage, tokens, and provider stats for projects you can access.

Personal-assistant turns are included in these totals. The main answer, conversation compaction, specialist consultation, final synthesis, memory extraction, and voice transcription are recorded as separate assistant-* request types. Provider-reported token counts are used when available; if a streaming provider omits usage metadata, Kroov records a conservative estimate instead of silently showing zero.

Workspace-backed AgentRun calls and in-process ServiceAgent calls are included too, including when they are launched by a scheduled task or an event automation. They appear as agent-run and service-agent request types. Each model call is recorded separately, so a paused run that later resumes does not re-count its earlier calls.

Costs​

Open Observe → Costs to break down spend:

  • By request type, provider, project, or individual request
  • Summary totals for the selected window

Use these views when tuning budgets on sessions, scheduled tasks, or project ceilings.

Logs​

Observe → Logs lists request logs (filters such as date range, prompt text, external ids). Open a row for detail, including requestId useful when debugging API failures.

API-key callers can also fetch project-scoped logs via GET /api/ai/logs.

Chat history​

Observe → History (admin) reviews chat sessions across users for operational debugging. End users see their own sessions through chat/session UIs rather than the admin history tool.

Tips​

  • Correlate API errors with Dashboard/requestId and, for agents/sessions, the SSE event stream.
  • noLog hides prompt/response text when the project allows it — metrics rows remain.
  • Assistant metrics are attached to the active project for Dashboard, Logs, and Costs, while quota consumption is charged once to the owner's organization so the platform admin sees the same usage.
  • Private assistant workspaces stay hidden from general project and Studio listings, but their owner can see their requests in Dashboard, Logs, and Costs. The admin usage console reconciles current- month counters with durable request logs, including personal-workspace activity, so a temporary metering outage does not make already-recorded requests disappear.
  • Session, scheduled-task, workspace-agent, and service-agent metrics are attached to their project; that project's organization receives the matching monthly token usage.
  • Watch cost trends after enabling automations or scheduled tasks.