Monitor agent health and performance in Nora
View platform metrics, agent-level CPU and memory stats, activity events, cost tracking, and historical performance data for your agents in Nora.
Nora collects runtime metrics, activity events, and cost data for every agent you deploy. You can view a live snapshot of an agent’s resource usage, pull historical stats over configurable time windows, browse the activity event log, and check accumulated cost data — all from the dashboard or the monitoring API. This page explains what data is collected, how to read it, and the available time ranges for historical queries.
The platform-level monitoring endpoint returns aggregate statistics across all agents you can access, including directly owned agents and agents shared with you through workspaces. It includes totals for running agents, queued jobs, and recent activity.
GET /api/monitoring/metrics
Agent-level metrics
Each agent exposes a live stats snapshot and a historical stats series. Stats are collected every 10 seconds and retained for 24 hours.
Live stats
To fetch the current resource usage for a running agent:
GET /api/agents/:id/stats
| Field | Type | Description |
|---|
cpu_percent | number | Current CPU usage as a percentage across all cores |
memory_usage_mb | number | Actual memory in use (excluding cache), in megabytes |
memory_limit_mb | number | Container memory limit, in megabytes |
memory_percent | number | Memory usage as a percentage of the limit |
network_rx_mb | number | Total bytes received across all network interfaces, in megabytes |
network_tx_mb | number | Total bytes transmitted across all network interfaces, in megabytes |
disk_read_mb | number | Total block device read bytes, in megabytes |
disk_write_mb | number | Total block device write bytes, in megabytes |
pids | number | Current number of processes (PIDs) in the container |
uptime_seconds | number | Seconds since the container last started |
running | boolean | Whether the container is currently running |
Live stats require a running container. If the agent is stopped or has no container, the endpoint returns a 409 error.
Historical stats
To fetch a time series of stats for an agent, use the history endpoint with a time range:
GET /api/agents/:id/stats/history?range=15m
| Parameter | Window |
|---|
5m | Last 5 minutes |
15m | Last 15 minutes (default) |
30m | Last 30 minutes |
1h | Last 1 hour |
6h | Last 6 hours |
24h | Last 24 hours |
GET /api/agents/:id/stats/history?from=2026-04-10T08:00:00Z&to=2026-04-10T09:00:00Z
recorded_at timestamp. Results are ordered by recorded_at ascending and capped at 2000 rows per query.
Historical stat fields:
| Field | Description |
|---|
cpu_percent | CPU usage at that sample point |
memory_usage_mb | Memory in use at that sample point |
memory_limit_mb | Memory limit at that sample point |
memory_percent | Memory usage percentage at that sample point |
network_rx_mb | Cumulative network receive bytes |
network_tx_mb | Cumulative network transmit bytes |
disk_read_mb | Cumulative disk read bytes |
disk_write_mb | Cumulative disk write bytes |
pids | Process count at that sample point |
recorded_at | ISO 8601 timestamp of when the sample was taken |
Activity events
The events log records actions taken on agents and by agents — deployments, redeployments, errors, and other lifecycle events.
GET /api/monitoring/events
GET /api/monitoring/events?agentId=<agent-id>
GET /api/monitoring/events?limit=100
created_at descending (newest first).
Agent metrics summary
For a summarized view of an agent’s metrics over the default 24-hour window:
GET /api/agents/:id/metrics/summary
GET /api/agents/:id/metrics?type=cpu&since=2026-04-09T00:00:00Z
Agent cost tracking
Nora tracks token usage for each agent and estimates spend from model rates. The operator cost dashboard groups token spend by workspace, links each row back to the related agent, and reports a unique fleet total so an agent assigned to multiple workspaces is not double-counted. Each agent row can show token usage grouped by model.
To view the all-workspaces cost dashboard through the API:
GET /api/workspaces/cost?period_days=30
period_start=YYYY-MM-DD&period_end=YYYY-MM-DD for a custom UTC date range. The dashboard also supports searching by workspace, agent, model, or provider.
The response includes workspaces[], unassigned.perAgent[], workspaceTotalUsd, uniqueFleetTotalUsd, and each agent’s cost_details.tokens. Use uniqueFleetTotalUsd for fleet-wide totals and workspace totals for team-level budgeting.
Token cost uses COST_MODEL_RATES_JSON when the metric row includes model metadata. Rows without model metadata are grouped as Unknown model and priced with COST_PER_1K_TOKENS.
To view the accumulated cost data for one agent:
The response includes token totals and usage breakdowns. If the agent exists but has no recorded token usage in the selected window, totals are zero.
To view one workspace’s cost breakdown:
GET /api/workspaces/:id/cost?period_days=30
GET /api/monitoring/performance
since parameter:
GET /api/monitoring/performance?since=2026-04-10T06:00:00Z
Use the 24-hour historical stats window combined with the activity events log to correlate performance dips with specific deployment or lifecycle events.
