diff --git a/docs/use-cases/observability/clickstack/event_patterns.md b/docs/use-cases/observability/clickstack/event_patterns.md
new file mode 100644
index 00000000000..4fd4d08d6bd
--- /dev/null
+++ b/docs/use-cases/observability/clickstack/event_patterns.md
@@ -0,0 +1,38 @@
+---
+slug: /use-cases/observability/clickstack/event_patterns
+title: 'Event Patterns with ClickStack'
+sidebar_label: 'Event Patterns'
+pagination_prev: null
+pagination_next: null
+description: 'Event Patterns with ClickStack'
+---
+
+import Image from '@theme/IdealImage';
+import event_patterns from '@site/static/images/use-cases/observability/event_patterns.png';
+import event_patterns_highlight from '@site/static/images/use-cases/observability/event_patterns_highlight.png';
+
+Event patterns in ClickStack 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.
+
+<Image img={event_patterns} alt="Event patterns" size="lg"/>
+
+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 - ClickStack adapts to your events automatically, regardless of format.
+
+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 {#accessing-event-patterns}
+
+Event patterns are available directly through the **Search** panel in ClickStack.  
+
+From the top-left **Analysis Mode** selector, choose **Event Patterns** to switch from the standard results table to a clustered view of similar events.  
+
+<Image img={event_patterns_highlight} alt="Event patterns" size="lg"/>
+
+This provides an alternative to the default **Results Table** which allows users to scroll through every individual log or trace.
+
+## Recommendations {#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 are also particularly powerful for summarizing error messages, where repeated errors with varying IDs or payloads are grouped into concise clusters.  
+
+For a live example, see how event patterns are used in the [Remote Demo Dataset](/use-cases/observability/clickstack/getting-started/remote-demo-data#identify-error-patterns).
diff --git a/sidebars.js b/sidebars.js
index 07dea2c7035..d1e9524847a 100644
--- a/sidebars.js
+++ b/sidebars.js
@@ -1555,6 +1555,7 @@ const sidebars = {
         "use-cases/observability/clickstack/ttl",
         "use-cases/observability/clickstack/search",
         "use-cases/observability/clickstack/dashboards",
+        "use-cases/observability/clickstack/event_patterns",
         "use-cases/observability/clickstack/alerts",
         "use-cases/observability/clickstack/production",
         {
diff --git a/static/images/use-cases/observability/event_patterns.png b/static/images/use-cases/observability/event_patterns.png
new file mode 100644
index 00000000000..eea59f17387
Binary files /dev/null and b/static/images/use-cases/observability/event_patterns.png differ
diff --git a/static/images/use-cases/observability/event_patterns_highlight.png b/static/images/use-cases/observability/event_patterns_highlight.png
new file mode 100644
index 00000000000..ba82e6836f1
Binary files /dev/null and b/static/images/use-cases/observability/event_patterns_highlight.png differ