value -> metric_value

Author: ericallam

apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.query/ExamplesContent.tsx

@@ -81,7 +81,7 @@ LIMIT 100`,
     description: "Track process CPU utilization bucketed over time.",
     query: `SELECT
   timeBucket(),
-  avg(value) AS avg_cpu
+  avg(metric_value) AS avg_cpu
 FROM metrics
 WHERE metric_name = 'process.cpu.utilization'
 GROUP BY timeBucket
@@ -95,7 +95,7 @@ LIMIT 1000`,
     description: "Average memory usage per task identifier over the last 7 days.",
     query: `SELECT
   task_identifier,
-  avg(value) AS avg_memory
+  avg(metric_value) AS avg_memory
 FROM metrics
 WHERE metric_name = 'system.memory.usage'
   AND bucket_start > now() - INTERVAL 7 DAY

apps/webapp/app/v3/querySchemas.ts

@@ -498,8 +498,9 @@ export const metricsSchema: TableSchema = {
         coreColumn: true,
       }),
     },
-    value: {
-      name: "value",
+    metric_value: {
+      name: "metric_value",
+      clickhouseName: "value",
       ...column("Float64", {
         description: "The metric value",
         example: "0.75",

apps/webapp/app/v3/services/aiQueryService.server.ts

@@ -454,7 +454,7 @@ Only use explicit \`toStartOfHour\`/\`toStartOfDay\` etc. if the user specifical
 - Filter by run: WHERE run_id = 'run_abc123'
 - Filter by task: WHERE task_identifier = 'my-task'
 - 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
-- Use \`value\` — the metric's observed value
+- Use \`metric_value\` — the metric's observed value
 - Use prettyFormat(expr, 'bytes') to tell the UI to format values as bytes (e.g., "1.50 GiB") — keeps values numeric for charts
 - Use prettyFormat(expr, 'percent') for percentage values
 - 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
 
 \`\`\`sql
 -- CPU utilization over time for a task
-SELECT timeBucket(), task_identifier, prettyFormat(avg(value), 'percent') AS avg_cpu
+SELECT timeBucket(), task_identifier, prettyFormat(avg(metric_value), 'percent') AS avg_cpu
 FROM metrics
 WHERE metric_name = 'process.cpu.utilization'
 GROUP BY timeBucket, task_identifier
@@ -474,7 +474,7 @@ LIMIT 1000
 
 \`\`\`sql
 -- Peak memory usage per run
-SELECT run_id, task_identifier, prettyFormat(max(value), 'bytes') AS peak_memory
+SELECT run_id, task_identifier, prettyFormat(max(metric_value), 'bytes') AS peak_memory
 FROM metrics
 WHERE metric_name = 'process.memory.usage'
 GROUP BY run_id, task_identifier
@@ -589,7 +589,7 @@ LIMIT 1000
 ### Common Metrics Patterns
 - Filter by metric: WHERE metric_name = 'process.cpu.utilization'
 - 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
-- Use \`value\` — the metric's observed value
+- Use \`metric_value\` — the metric's observed value
 - Use prettyFormat(expr, 'bytes') for memory metrics (including nodejs.heap.*), prettyFormat(expr, 'percent') for CPU utilization
 - prettyFormat does NOT change the SQL — it only adds a display hint for the UI