altinity-expert-clickhouse-text-log

Analyze ClickHouse server logs and traces from system.text_log and system.trace_log.

42|7|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/ntk148v/clicklens --skill altinity-expert-clickhouse-text-log
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: altinity-expert-clickhouse-text-log
Source: https://github.com/ntk148v/clicklens/tree/main/.agent/skills/altinity-expert-clickhouse-text-log
Command: npx skills add https://github.com/ntk148v/clicklens --skill altinity-expert-clickhouse-text-log

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the investigation of ClickHouse server logs and traces, enabling faster diagnosis of issues and performance problems.

Core Features & Use Cases

  • Analyze log levels and message distribution from system.text_log to identify incident patterns.
  • Inspect recent critical and error messages, track trends, and correlate with relevant components.
  • Perform trace and stack analysis using system.trace_log to locate root causes and bottlenecks.
  • Validate log configurations and health by checking server settings and table metadata in system tables.

Quick Start

Query system.text_log and system.trace_log for the last hour to begin tracing incidents and performance events.

Frequently Asked Questions about altinity-expert-clickhouse-text-log

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze ClickHouse system.text_log to identify recent critical errors?

To analyze ClickHouse system.text_log, query recent critical and error messages to track incident trends and correlate them with relevant server components. This approach surfaces actionable insights into log level distributions and message patterns.

What is the best way to perform trace analysis using ClickHouse system.trace_log?

Performing trace analysis with ClickHouse system.trace_log involves inspecting stack traces and memory traces to locate root causes and performance bottlenecks. SQL-based patterns guide targeted investigations across trace events to isolate exact query issues.

Can I use SQL to diagnose memory bottlenecks in ClickHouse trace logs?

Yes, you can use SQL to diagnose memory bottlenecks by querying memory traces within ClickHouse trace logs. Analyzing system.trace_log entries allows you to pinpoint specific memory allocations and stack events causing performance degradation.

How do I check ClickHouse log configurations and table metadata in system tables?

Validate ClickHouse log configurations by querying server settings and table metadata directly within system tables. Checking these system tables ensures proper log health and confirms that diagnostic data captures the correct operational telemetry.

Does this approach work for investigating ClickHouse crash logs and system errors?

Yes, this approach works for investigating ClickHouse crash logs and system errors. It provides SQL-based patterns to analyze system.crash_log alongside text logs, enabling comprehensive root cause analysis for server failures and unexpected terminations.

Why should I use system.text_log for ClickHouse diagnostics instead of external monitoring tools?

Using system.text_log for ClickHouse diagnostics provides direct, internal access to server logs and trace events without external tool latency. It enables immediate, SQL-driven correlation between log levels, trace events, and configuration states.