Skip to content

`maqpna top agents`

CPU, memory, model calls, tokens and cost summed per agent

Observe-o json | yaml

Synopsis#

maqpna top agents [-n NS | -A] [--sort-by cpu|memory|cost|tokens] [--gateway URL] [--no-headers]

Description#

From the help of maqpna top:

Running sessions with the CPU and memory of their sandbox pods (needs the metrics API, e.g. metrics-server) and, with a gateway, their model calls, tokens and cost. top agents sums them per agent. A column without its source shows "-".

Flags#

Flag	Type	Description	Default
`-A`, `--all-namespaces`	switch	all namespaces	none
`--allow-gateway-mismatch`	switch	send the context's login token to a gateway other than the one it was issued for (env MAQPNA_ALLOW_GATEWAY_MISMATCH=1)	none
`--field-selector`	string	field selector evaluated on any field (spec.agentRef=coder,status.phase!=Failed)	none
`--gateway`	string	gateway base URL (env MAQPNA_GATEWAY_URL; default: the context's gateway)	none
`-l`, `--selector`	string	label selector (e.g. app=coder,tier!=t0); Kubernetes kinds	none
`-n`, `--namespace`	string	namespace	`default`
`--no-headers`	switch	omit the header row	none
`--oidc-token-file`	string	file holding an OIDC access token for the admin API (env MAQPNA_OIDC_TOKEN_FILE); wins over `--token`	none
`--sort-by`	string	cpu \| memory \| cost \| tokens	none
`--token`	string	static admin token (env MAQPNA_ADMIN_TOKEN; dev/break-glass)	none

The global flags (--context, -o, --no-color, ...) work with every command.

Examples#

$ maqpna top agents -A --gateway https://gw.example.com

What happens when you run it#

Talks to the gateway: --gateway, else MAQPNA_GATEWAY_URL, else the current context's gateway (maqpna context).
Authenticates to the admin API with the token stored by maqpna login, --oidc-token-file, or a static --token (MAQPNA_ADMIN_TOKEN).
Prints a table by default; -o json or -o yaml print the data, and --jq EXPR filters the JSON.

Exit codes#

Code	Meaning
`0`	success
`1`	error (the message says what failed, with a hint when there is one)
`2`	usage error: unknown flag, missing argument or bad value; the synopsis is printed
`3`	a check failed, a change is blocked, or a result did not match (tamper, policy mismatch) (not used by this command)