📣

TiDB Cloud Premium is now in public preview. Unlimited growth, instant elasticity, advanced security for enterprise workloads. Try it out →

system_history.log_history

System operations audit trail - Raw log repository from all TiDB Cloud Lake nodes and components. Foundation for operational intelligence:

System Monitoring: Track system health, performance, and resource usage
Troubleshooting: Debug issues with detailed error logs and system events
Operational Analytics: Analyze system behavior patterns and trends
Root Cause Analysis: Investigate system failures and performance bottlenecks

Note

Fields

Field	Type	Description
timestamp	TIMESTAMP	The timestamp when the log entry was recorded
path	VARCHAR	Source file path and line number of the log
target	VARCHAR	Target module or component of the log
log_level	VARCHAR	Log level (e.g., `INFO`, `ERROR`)
cluster_id	VARCHAR	Identifier of the cluster
node_id	VARCHAR	Identifier of the node
warehouse_id	VARCHAR	Identifier of the warehouse
query_id	VARCHAR	Query ID associated with the log
message	VARCHAR	Log message content
fields	VARIANT	Additional fields (as a JSON object)
batch_number	BIGINT	Internal use, no special meaning

Note: The message field stores plain text logs, while the fields field stores logs in JSON format.

For example, the fields field of a log entry might look like:

fields: {"node_id":"8R5ZMF8q0HHE6x9H7U1gr4","query_id":"72d2319a-b6d6-4b1d-8694-670137a40d87","session_id":"189fd3e2-e6ac-48c3-97ef-73094c141312","sql":"select * from system_history.log_history"}

the message field of another log entry might appear as follows:

message: [HTTP-QUERY] Preparing to plan SQL query

system_history.log_history

Fields

Was this page helpful?