Events
The greptime_private.events table stores events recorded while GreptimeDB runs. It helps operators inspect DDL changes and background procedures without searching service logs.
GreptimeDB writes event records asynchronously on a best-effort basis. Records are normally flushed every five seconds, so a recent operation might not be visible immediately. Event recording should not be treated as the operation's success acknowledgement.
Configure event recording
See Event recording for configuration options and the event types supported by standalone, Frontend, and Metasrv.
Query events
When the event recorder writes its first event, it creates the
greptime_private.events system table. If an existing table is missing columns
from the current event schema, the recorder adds them. It performs both actions
even when automatic table creation is disabled. Disabling event recording does
not remove an existing table. This query returns a table-not-found error only if
the table does not currently exist, for example because event recording was
disabled before any event was recorded or the table was dropped. The recorder
recreates the table when it writes another event.
Start with a bounded query while investigating a recent operation:
SELECT timestamp, type
FROM greptime_private.events
WHERE timestamp >= now() - INTERVAL '1' hour
ORDER BY timestamp DESC
LIMIT 20;
Use the following pages for focused queries and event details: