anomaly-detection

Detect abnormal behavior in self-hosted ClickHouse clusters using 1-hour metrics against a 24-hour baseline.

255|42|Updated Nov 16, 2023
One-click install
npx skills add https://github.com/chmonitor/chmonitor --skill anomaly-detection-chmonitor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: anomaly-detection
Source: https://github.com/chmonitor/chmonitor/tree/main/.agents/skills/anomaly-detection
Command: npx skills add https://github.com/chmonitor/chmonitor --skill anomaly-detection-chmonitor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually reviewing ClickHouse system metrics to identify unusual cluster behavior is time-consuming and prone to missing subtle performance regressions, error spikes, or resource issues that impact production workloads.

Core Features & Use Cases

  • Baseline Comparison Anomaly Detection: Compares recent 1-hour activity to a preceding 24-hour baseline to flag statistically significant deviations.
  • Multi-Domain Monitoring: Covers error rate spikes, query duration regressions, query volume anomalies, memory usage outliers, part count explosions, and replication lag.
  • Actionable Interpretation: Provides clear thresholds to distinguish real anomalies from statistical noise, plus cross-references to specialized skills for root cause resolution. Use case: A ClickHouse operator can use this skill to quickly confirm if a recent deployment caused a 2x increase in query failures or p95 latency without manually parsing hours of query logs.

Quick Start

Use the anomaly-detection skill to run the error rate spike check on your ClickHouse cluster to determine if recent query failures are abnormally high compared to the previous 24-hour baseline.

Frequently Asked Questions about anomaly-detection

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

FAQPage Schema
How do I detect ClickHouse query performance regressions against historical data?

ClickHouse anomaly detection identifies error rate spikes by comparing recent 1-hour query failure metrics against a 24-hour baseline. This helps quickly confirm if recent deployments caused abnormally high query failures compared to historical norms.

What is the best way to monitor ClickHouse replication lag and part count explosions?

ClickHouse anomaly detection provides actionable interpretation by applying clear thresholds to distinguish statistical noise from actionable cluster issues. It cross-references related troubleshooting skills for root cause resolution of detected performance regressions or error spikes.

Can I use baseline comparison for self-hosted ClickHouse cluster monitoring?

You can spot ClickHouse memory usage outliers by comparing recent 1-hour memory metrics against a preceding 24-hour baseline. This identifies statistically significant deviations that indicate abnormal resource consumption impacting production workloads.

How do I identify ClickHouse error rate spikes after a recent deployment?

Query volume anomaly flagging in ClickHouse compares recent 1-hour query activity against a 24-hour baseline. This detects statistically significant deviations in query execution volume, identifying sudden workload spikes or drops without reviewing hours of system metrics.