> ## Documentation Index
> Fetch the complete documentation index at: https://clickhouse.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Event patterns with ClickHouse Observability

> Event patterns with ClickHouse Observability

Event patterns in ClickHouse Observability allow you to quickly make sense of large volumes of logs or traces by automatically clustering similar messages together, so instead of digging through millions of individual events, you only need to review a small number of meaningful groups.

![Event Patterns in Search with trend charts, counts, severity levels, and grouped log messages](https://mintcdn.com/private-7c7dfe99/dW6bcEakZdn3a5oP/images/clickstack/observability-event-patterns.png?fit=max\&auto=format\&n=dW6bcEakZdn3a5oP\&q=85\&s=54d08acf37b75583815f1305b62303d4)

This makes it much easier to spot which errors or warnings are new, which are recurring, and which are driving sudden spikes in log volume. Because the patterns are generated dynamically, you don't need to define regular expressions or maintain parsing rules.

Beyond incident response, this high-level view also helps you identify noisy log sources that can be trimmed to reduce cost, discover the different types of logs a service produces, and more quickly answer whether the system is already emitting the signals you care about.

## Accessing event patterns

Event patterns are available directly through the **Search** panel in ClickHouse Observability.

Under **Analysis Mode** on the left, select **Event Patterns** to switch from the standard results table to a clustered view of similar events.

![Event Patterns highlighted under Analysis Mode in Search](https://mintcdn.com/private-7c7dfe99/dW6bcEakZdn3a5oP/images/clickstack/observability-event-patterns-highlight.png?fit=max\&auto=format\&n=dW6bcEakZdn3a5oP\&q=85\&s=a642531f9a6df826b888ea1fd0697889)

This provides an alternative to the default **Results Table** which allows you to scroll through every individual log or trace.

## Recommendations

Event patterns are most effective when applied to **narrowed subsets** of your data. For example, filtering down to a single service before enabling event patterns will usually surface more relevant and interesting messages than applying patterns across thousands of services at once.

They're also particularly powerful for summarizing error messages, where repeated errors with varying IDs or payloads are grouped into concise clusters.