Metrics
Scrape Archestra's Prometheus metrics to track model spend, tool calls, guardrails, agent runs, and platform health. Choose a reference below to look up metric names, labels, and aggregation behavior.
Guardrails and OpenAPPA metrics use the same scrape endpoints and authentication as all other Archestra metrics.
Scraping
Each process serves its own registry, so scrape every pod:
| Process | Endpoint | Emits |
|---|---|---|
| Web | http://<pod>:9050/metrics | Requests served by the web tier: LLM, MCP, Guardrails, chat, coding agents, HTTP |
| Worker | http://<pod>:9000/metrics | Knowledge Base syncs and embeddings, the task queue, scheduled tasks, and the LLM and MCP calls they make |
The Helm chart runs the worker as its own Deployment by default. Sum counters across web and worker pods: an agent run from a schedule reports its LLM metrics from a worker pod.
ARCHESTRA_ changes the web port. Worker pods serve metrics on their API port, 9000.
Authentication
The endpoint is open by default. Set ARCHESTRA_ to require a bearer token on web and worker pods. Requests without it get 401.
scrape_configs:
- job_name: archestra
authorization:
type: Bearer
credentials: <ARCHESTRA_METRICS_SECRET>
kubernetes_sd_configs:
- role: pod
Helm Pod Annotations
For a Prometheus that discovers pods by annotation, add these to the chart values:
archestra:
podAnnotations:
prometheus.io/scrape: "true"
prometheus.io/port: "9050"
prometheus.io/path: /metrics
The chart rewrites prometheus.io/port to 9000 on worker pods.
To check a pod, run curl -s http://<pod>:9050/metrics | grep "# HELP llm_". Add -H "Authorization: Bearer <secret>" when a secret is set.
Labels
Most LLM metrics share these labels:
| Label | Values |
|---|---|
provider, model | The LLM provider and model, for example anthropic and claude-sonnet-4-5 |
agent_, agent_ | The Archestra agent that made the call. All LLM Proxy traffic reports agent_name="LLM Proxy". Knowledge Base calls report agent_name="Knowledge Base" with an empty agent_. |
agent_ | agent, llm_, mcp_, or profile |
organization_ | The owning organization |
source | Where the request came from, for example api, chat, chatops:slack, email, schedule-trigger, app:llm_complete, knowledge:embedding, or knowledge:reranker |
MCP tool call metrics carry agent_, agent_, agent_, mcp_, tool_, and status (success or error).
Agent Labels
Go to an agent's Advanced tab and add a key and value under Labels. Each agent label becomes an extra label on the LLM, MCP, and agent_ metrics. Prometheus allows only letters, digits, and underscores in label names, so other characters become _: cost-center turns into cost_.
Dimensions Without Labels
LLM and MCP request metrics do not carry user, skill, app, or client-supplied identity labels, except where noted below. Limit metrics separately identify the configured budget target. Use these sources for request attribution:
- Users: per-user statistics, or the
archestra.user.*span attributes. - Skills and apps: per-skill and per-app statistics. App LLM spend shows in the LLM metrics as
source="app:llm_complete". - Client-supplied agent IDs from the
X-Archestra-Agent-Idheader: thearchestra.external_agent_idspan attribute. Onlyagent_carries it as a label.runs_ total - Credentials: the
archestra.virtual_key.idspan attribute.