AdminMetrics

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:

ProcessEndpointEmits
Webhttp://<pod>:9050/metricsRequests served by the web tier: LLM, MCP, Guardrails, chat, coding agents, HTTP
Workerhttp://<pod>:9000/metricsKnowledge 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_METRICS_PORT changes the web port. Worker pods serve metrics on their API port, 9000.

Authentication

The endpoint is open by default. Set ARCHESTRA_METRICS_SECRET to require a bearer token on web and worker pods. Requests without it get 401.

yaml
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:

yaml
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:

LabelValues
provider, modelThe LLM provider and model, for example anthropic and claude-sonnet-4-5
agent_id, agent_nameThe 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_id.
agent_typeagent, llm_proxy, mcp_gateway, or profile
organization_idThe owning organization
sourceWhere 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_id, agent_name, agent_type, mcp_server_name, tool_name, 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_runs_total metrics. Prometheus allows only letters, digits, and underscores in label names, so other characters become _: cost-center turns into cost_center.

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:

Explore