Querying in ClickHouse CloudThe data in this system table is held locally on each node in ClickHouse Cloud. Obtaining a complete view of all data, therefore, requires the
clusterAllReplicas function. See here for further details.Description
Contains error codes with the number of times they have been triggered. To show all possible error codes, including ones which were not triggered, set setting system_events_show_zero_values to 1.Columns
name(String) — Name of the error (errorCodeToName).code(Int32) — Code number of the error.value(UInt64) — The number of times this error happened.last_error_time(DateTime) — The time when the last error happened.last_error_message(String) — Message for the last error.last_error_format_string(String) — Format string for the last error.last_error_trace(Array(UInt64)) — A stack trace of the last error. On ELF platforms except FreeBSD, addresses inside the main ClickHouse binary are stored as physical file offsets, and other addresses are virtual memory addresses inside the ClickHouse server process.remote(UInt8) — Remote exception (i.e. received during one of the distributed queries).query_id(String) — Id of a query that caused an error (if available).last_error_symbols(Array(LowCardinality(String))) — Demangled symbol names corresponding to last_error_trace.last_error_lines(Array(LowCardinality(String))) — File names with line numbers corresponding to last_error_trace.
last_error_symbols and last_error_lines are resolved from the binary’s symbol table and debug info.
last_error_symbols is populated wherever the symbol table is available (Linux and macOS builds).
last_error_lines additionally requires DWARF debug info - read directly from the binary on Linux, or from a co-located .dSYM bundle on macOS - so it is empty when that debug info is not available. Both arrays are empty on platforms without introspection support (for example FreeBSD).
Example
Query
Response