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 history of error values from tablesystem.errors, periodically flushed to disk.
Columns
hostname(LowCardinality(String)) — Hostname of the server executing the query.clickhouse_version(LowCardinality(String)) — Version of the ClickHouse server that produced the row.system_processor(LowCardinality(String)) — CPU architecture of the ClickHouse server that produced the row.event_date(Date) — Event date.event_time(DateTime) — Event time.code(Int32) — Error code.error(LowCardinality(String)) — Error name.value(UInt64) — Number of errors happened in time interval.remote(UInt8) — Remote exception (i.e. received during one of the distributed queries).last_error_time(DateTime) — The time when the last error happened.last_error_message(String) — Message for the last error.last_error_query_id(String) — Id of a query that caused the last error (if available).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.
Example
See Also
- error_log setting — Enabling and disabling the setting.
- system.errors — Contains error codes with the number of times they have been triggered.
- Monitoring — Base concepts of ClickHouse monitoring.