@@ -453,8 +453,8 @@ Only use explicit \`toStartOfHour\`/\`toStartOfDay\` etc. if the user specifical
453453- Filter by metric name: WHERE metric_name = 'process.cpu.utilization'
454454- Filter by run: WHERE run_id = 'run_abc123'
455455- Filter by task: WHERE task_identifier = 'my-task'
456- - Available metric names: process.cpu.utilization, process.cpu.time, process.memory.usage, system.memory.usage, system.memory.utilization, system.network.io, system.network.dropped, system.network.errors, nodejs.event_loop.utilization, nodejs.event_loop.delay.p50, nodejs.event_loop.delay.p99 , nodejs.event_loop.delay.max, nodejs.heap.used, nodejs.heap.total
457- - Use max_value or last_value for gauges (CPU utilization, memory usage), sum_value for counters (CPU time, network IO)
456+ - Available metric names: process.cpu.utilization, process.cpu.time, process.memory.usage, system.memory.usage, system.memory.utilization, system.network.io, system.network.dropped, system.network.errors, nodejs.event_loop.utilization, nodejs.event_loop.delay.p95 , nodejs.event_loop.delay.max, nodejs.heap.used, nodejs.heap.total
457+ - Use \`value\` — the metric's observed value
458458- Use prettyFormat(expr, 'bytes') to tell the UI to format values as bytes (e.g., "1.50 GiB") — keeps values numeric for charts
459459- Use prettyFormat(expr, 'percent') for percentage values
460460- prettyFormat does NOT change the SQL — it only adds a display hint
@@ -464,7 +464,7 @@ Only use explicit \`toStartOfHour\`/\`toStartOfDay\` etc. if the user specifical
464464
465465\`\`\`sql
466466-- CPU utilization over time for a task
467- SELECT timeBucket(), task_identifier, prettyFormat(avg(max_value ), 'percent') AS avg_cpu
467+ SELECT timeBucket(), task_identifier, prettyFormat(avg(value ), 'percent') AS avg_cpu
468468FROM metrics
469469WHERE metric_name = 'process.cpu.utilization'
470470GROUP BY timeBucket, task_identifier
@@ -474,7 +474,7 @@ LIMIT 1000
474474
475475\`\`\`sql
476476-- Peak memory usage per run
477- SELECT run_id, task_identifier, prettyFormat(max(max_value ), 'bytes') AS peak_memory
477+ SELECT run_id, task_identifier, prettyFormat(max(value ), 'bytes') AS peak_memory
478478FROM metrics
479479WHERE metric_name = 'process.memory.usage'
480480GROUP BY run_id, task_identifier
@@ -589,7 +589,7 @@ LIMIT 1000
589589### Common Metrics Patterns
590590- Filter by metric: WHERE metric_name = 'process.cpu.utilization'
591591- Available metric names: process.cpu.utilization, process.cpu.time, process.memory.usage, system.memory.usage, system.memory.utilization, system.network.io, system.network.dropped, system.network.errors, nodejs.event_loop.utilization, nodejs.event_loop.delay.p50, nodejs.event_loop.delay.p99, nodejs.event_loop.delay.max, nodejs.heap.used, nodejs.heap.total
592- - Use max_value or last_value for gauges (CPU utilization, memory usage), sum_value for counters (CPU time, network IO)
592+ - Use \`value\` — the metric's observed value
593593- Use prettyFormat(expr, 'bytes') for memory metrics (including nodejs.heap.*), prettyFormat(expr, 'percent') for CPU utilization
594594- prettyFormat does NOT change the SQL — it only adds a display hint for the UI
595595
0 commit comments