For the complete documentation index, see llms.txt. This page is also available as Markdown.
NewMonitoringObservability
Control Center
Manage platform governance, monitoring, access, usage, quality, billing, and audit.
Control Center is the account-wide administration and monitoring surface of the Qore platform. It's where you watch how your apps and agents are used, evaluate the quality of their output, enforce guardrails and kill switches, inspect logs, manage billing, and control who has access.
Control Center as an operator sees it, with the modules listed below in the left navigation.
At a glance
What it's for: monitoring, quality control, governance, and administration across your whole Qore account — not building apps or agents (that happens in Studio), but running and overseeing them.
Who uses it: account admins and operators day-to-day; developers and integrators for API keys, logs, and permissions; anyone who needs to see usage, cost, or audit history.
How it's organized: six modules, each holding two to four screens.
Scope: everything in Control Center is account-wide and can be filtered by workspace.
Control Center modules
Explore the areas you work with:
Observability — who's using your apps and agents, how much, and with what outcomes.
Evaluation & Quality — define evaluators that score agent output, watch them run on live traffic, and review flagged executions by hand.
Controls & Audit — see guardrail results, stop agents in an emergency, and read the account-wide change log.
Logs & Data — trace every LLM call, inbound and outbound request, and database operation.
Billing — track credit usage and set hard limits and alerts.
Account Settings — manage users and their roles, group them into teams scoped to product spaces, and issue API keys.
How Control Center fits together
The modules are separate views over the same account activity, so one agent run shows up in several places, each from a different angle: as a thread in Agent Analytics, a scored execution in Online Eval, a task in Human Review when its confidence is low, a set of input and output checks in Guardrails, the model calls it made in LLM Logs, and the records it changed in Audit Trails and DB Query Logs.
Knowing which module answers which question is most of what it takes to work quickly here:
Is anyone using this? → Observability.
Is the output any good? → Evaluation & Quality.
Is it safe, and who changed what? → Controls & Audit.
What exactly did it call and write? → Logs & Data.
