Skip to content

This feature is currently in Preview.

Query Patterns and Best Practices

SELECT REASONER_NAME, MEMORY_UTILIZATION, TIMESTAMP
FROM relationalai.observability_preview.logic_reasoner__memory_utilization
WHERE timestamp >= DATEADD(minute, -5, CURRENT_TIMESTAMP())
ORDER BY timestamp DESC;
SELECT
REASONER_NAME,
DATE_TRUNC('hour', TIMESTAMP) AS hour,
AVG(CPU_UTILIZATION) AS avg_cpu,
MAX(CPU_UTILIZATION) AS max_cpu
FROM relationalai.observability_preview.logic_reasoner__cpu_utilization
WHERE timestamp >= DATEADD(hour, -24, CURRENT_TIMESTAMP())
GROUP BY REASONER_NAME, hour
ORDER BY hour DESC;
SELECT
REASONER_NAME,
DATE_TRUNC('day', TIMESTAMP) AS day,
AVG(MEMORY_UTILIZATION) AS avg_memory,
MAX(MEMORY_UTILIZATION) AS peak_memory
FROM relationalai.observability_preview.logic_reasoner__memory_utilization
WHERE timestamp >= DATEADD(day, -7, CURRENT_TIMESTAMP())
GROUP BY REASONER_NAME, day
ORDER BY day DESC;
SELECT *
FROM relationalai.observability_preview.logic_reasoner__demand
WHERE REASONER_NAME = 'my_reasoner'
AND timestamp >= DATEADD(hour, -1, CURRENT_TIMESTAMP());
SELECT
m.REASONER_NAME,
m.TIMESTAMP,
m.MEMORY_UTILIZATION,
c.CPU_UTILIZATION,
d.DEMAND
FROM relationalai.observability_preview.logic_reasoner__memory_utilization m
JOIN relationalai.observability_preview.logic_reasoner__cpu_utilization c
ON m.REASONER_ID = c.REASONER_ID
AND m.TIMESTAMP = c.TIMESTAMP
JOIN relationalai.observability_preview.logic_reasoner__demand d
ON m.REASONER_ID = d.REASONER_ID
AND m.TIMESTAMP = d.TIMESTAMP
WHERE m.TIMESTAMP >= DATEADD(hour, -1, CURRENT_TIMESTAMP());