altinity-expert-clickhouse-logs

Detect TTL misconfigurations and disk pressure in ClickHouse system log tables.

16|2|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/Altinity/Skills --skill altinity-expert-clickhouse-logs-altinity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: altinity-expert-clickhouse-logs
Source: https://github.com/Altinity/Skills/tree/main/altinity-expert-clickhouse/skills/altinity-expert-clickhouse-logs
Command: npx skills add https://github.com/Altinity/Skills --skill altinity-expert-clickhouse-logs-altinity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ClickHouse system logs can grow without TTL discipline, leading to disk pressure and RCA gaps. This skill analyzes TTL configurations, log freshness, and cleanup readiness to prevent data loss and performance issues.

Core Features & Use Cases

  • TTL health checks for system logs (query_log, part_log, trace_log) to surface misconfigurations.
  • Disk usage analysis and cleanup recommendations to maintain healthy storage.
  • RCA-ready diagnostics by validating log data freshness and retention policies.
  • Use Case: Run against a cluster with noisy logs to detect TTL gaps and propose actionable TTL adjustments.

Quick Start

Run the skill to evaluate current system log tables and print recommended TTL values and cleanup actions.

Frequently Asked Questions about altinity-expert-clickhouse-logs

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

FAQPage Schema
How do I check ClickHouse system log TTL configurations and disk usage?

You can check ClickHouse system log TTL configurations and disk usage by running SQL checks against system tables to calculate log lag, detect missing TTL policies, and assess overall disk pressure for cleanup readiness.

What causes disk pressure from ClickHouse system logs?

ClickHouse system logs can grow indefinitely without TTL discipline, leading to severe disk pressure and RCA gaps. Validating log data freshness and retention policies prevents data loss and performance degradation.

How do I detect stale logs and missing TTL in ClickHouse query_log and part_log?

Run TTL health checks against system log tables like query_log, part_log, and trace_log to surface misconfigurations, calculate data lag, and identify stale logs lacking proper retention policies.

Do I need cluster access to run ClickHouse log diagnostics and RCA workflows?

Yes, you need access to ClickHouse system tables across your cluster to execute the SQL checks that calculate TTL presence, data lag, and disk usage for effective RCA workflows.

What is the best way to clean up noisy ClickHouse system logs?

The best way to clean up noisy ClickHouse system logs is to evaluate current tables, identify TTL gaps, and apply recommended TTL adjustments to maintain healthy storage and prevent disk pressure.