docs mvp

docs/sources/patterns/_index.md

@@ -0,0 +1,96 @@
+---
+aliases:
+  - /docs/explore-apps/logs/patterns
+description: 
+keywords:
+  - Logs
+  - Log Patterns
+  - Explore
+  - Patterns
+  - Drain
+  - Categorization
+  - Analysis
+menuTitle: Log patterns
+title: Log patterns
+weight: 800
+---
+
+# Log patterns
+
+Log patterns allow you to work with groups of similar log lines. They are automatically extracted when your logs are ingested.
+
+The Explore Logs app shows you the patterns alongside their log volumes. From this view, you can investigate spikes and drill down to view the logs.
+
+## More use cases
+
+Log patterns allow you to:
+
+* Browse the log volume over time of different types of logs.
+* Simplify log management by grouping similar log entries.
+* Enhance log searches by focusing on relevant patterns.
+* Improve troubleshooting efficiency by highlighting critical log lines.
+* Reduce storage requirements by minimizing log data.
+* Filter out noisy log lines during exploration.
+* Identify specific log lines for targeted analysis.
+
+## Quick guides
+
+We've outlined the steps you'll need to take to perform these common use cases.
+
+### Browse log volumes by type
+
+
+
+### Targetted analysis
+
+If you know the kind of log line you're looking for, Log patterns are an easy way to get everything else out of the way.
+
+To view only a specific set of patterns, perform the following steps:
+
+1. Go to **Explore > Logs**
+2. Select the relevant **Service**
+3. Open the **Patterns** tab
+4. Identify a pattern that matches the type of logs you're interested in
+5. Select **Include**
+6. Go to the **Logs** tab and notice the filtered view
+
+### Hide noise
+
+To hide noisy log lines, perform the following steps:
+
+1. Go to **Explore > Logs**
+2. Select the relevant **Service**
+3. Open the **Patterns** tab
+4. Identify a pattern that represents noise in the logs
+5. Select **Exclude**
+6. Go to the **Logs** tab and notice the noise has been removed
+
+You can repeat steps 4 and 5 to exclude multiple patterns.
+
+## Pattern extraction
+
+Loki uses Drain, an online log template miner, to extract patterns from a stream of log lines.
+
+For example, if your services log lines like this:
+
+```
+duration=255ms trace_id=abc001 GET /path/to/endpoint/2
+user loaded: 25666
+user loaded: 14544
+duration=255ms trace_id=abc002 POST /path/to/endpoint/2
+user loaded: 25666
+duration=355ms trace_id=abc003 GET /path/to/endpoint/1
+duration=355ms trace_id=abc004 POST /path/to/endpoint/1
+duration=255ms trace_id=abc005 POST /path/to/endpoint/2
+user loaded: 89255
+duration=4244ms trace_id=abc006 GET /path/to/endpoint/1
+user loaded: 25666
+duration=255ms trace_id=abc007 GET /path/to/endpoint/2
+```
+
+Two patterns would emerge where the static tokens are preserved literally, and dynamic values are turned into placeholders:
+
+Pattern 1: `duration=<_> trace_id=<_> <_> /path/to/endpoint/<_>`
+
+Pattern 2: `user loaded: <_>`
+