system.events

Contains information about the number of events that have occurred in the system. For example, in the table, you can find how many SELECT queries were processed since the ClickHouse server started.

Columns:

  • event (String) — Event name.
  • value (UInt64) — Number of events occurred.
  • description (String) — Event description.

Example

  1. SELECT * FROM system.events LIMIT 5
  1. ┌─event─────────────────────────────────┬─value─┬─description────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
  2. Query 12 Number of queries to be interpreted and potentially executed. Does not include queries that failed to parse or were rejected due to AST size limits, quota limits or limits on the number of simultaneously running queries. May include internal queries initiated by ClickHouse itself. Does not count subqueries.
  3. SelectQuery 8 Same as Query, but only for SELECT queries.
  4. FileOpen 73 Number of files opened.
  5. ReadBufferFromFileDescriptorRead 155 Number of reads (read/pread) from a file descriptor. Does not include sockets.
  6. ReadBufferFromFileDescriptorReadBytes 9931 Number of bytes read from file descriptors. If the file is compressed, this will show the compressed data size.
  7. └───────────────────────────────────────┴───────┴────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

See Also

Original article