Skip to main content
Every query through SupaProxy is logged with full telemetry. There is no opt-out; observability is a core platform feature.

What gets logged

Each query creates an audit log entry with:
FieldDescription
WorkspaceWhich workspace handled the query
Consumer typeSlack, API, WhatsApp, or CLI
ChannelWhich channel or endpoint received the query
UserWho sent the query (name and ID)
QueryThe full query text
Tools calledWhich tools the agent invoked
Connections hitWhich connections were used
Knowledge chunksHow many knowledge chunks were retrieved
Tokens (input)Tokens sent to the language model
Tokens (output)Tokens generated by the language model
Cost (USD)Estimated cost of the query
Duration (ms)End-to-end response time
ErrorError message if the query failed

Workspace dashboard

The dashboard provides an overview of workspace health:
  • Tickets: open, cold, closed today, closed this week
  • Sentiment: average score and distribution
  • Compliance: total violations, recent violations, violations by rule
  • Knowledge gaps: topics with count and last seen date
  • Resolution: breakdown by status
  • Cost: today, this week, this month
  • Usage: query counts by period
  • Recent conversations: latest with stats
  • Categories: conversation breakdown by category
  • Channels: conversation breakdown by channel

Activity log

The Activity tab shows a paginated list of queries with:
  • User, query text, tools called, connections hit
  • Token usage, cost, duration
  • Timestamp
  • Errors (if any)
Supports pagination with configurable page size.

Conversation-level observability

Each conversation aggregates its audit entries into stats (see Conversations). This provides conversation-level metrics alongside the per-query audit trail.