logler 1.1.3__tar.gz → 1.2.0__tar.gz

{logler-1.1.3 → logler-1.2.0}/Cargo.lock

@@ -253,9 +253,9 @@ checksum = "37b2a672a2cb129a2e41c10b1224bb368f9f37a2b16b612598138befd7b37eb5"
 
 [[package]]
 name = "cc"
-version = "1.2.54"
+version = "1.2.55"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "6354c81bbfd62d9cfa9cb3c773c2b7b2a3a482d569de977fd0e961f6e7c00583"
+checksum = "47b26a0954ae34af09b50f0de26458fa95369a0d478d8236d3f93082b219bd29"
 dependencies = [
  "find-msvc-tools",
  "shlex",
@@ -310,9 +310,9 @@ dependencies = [
 
 [[package]]
 name = "clap"
-version = "4.5.54"
+version = "4.5.56"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "c6e6ff9dcd79cff5cd969a17a545d79e84ab086e444102a591e288a8aa3ce394"
+checksum = "a75ca66430e33a14957acc24c5077b503e7d374151b2b4b3a10c83b4ceb4be0e"
 dependencies = [
  "clap_builder",
  "clap_derive",
@@ -320,9 +320,9 @@ dependencies = [
 
 [[package]]
 name = "clap_builder"
-version = "4.5.54"
+version = "4.5.56"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "fa42cf4d2b7a41bc8f663a7cab4031ebafa1bf3875705bfaf8466dc60ab52c00"
+checksum = "793207c7fa6300a0608d1080b858e5fdbe713cdc1c8db9fb17777d8a13e63df0"
 dependencies = [
  "anstream",
  "anstyle",
@@ -332,9 +332,9 @@ dependencies = [
 
 [[package]]
 name = "clap_derive"
-version = "4.5.49"
+version = "4.5.55"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "2a0b5487afeab2deb2ff4e03a807ad1a03ac532ff5a2cee5d86884440c7f7671"
+checksum = "a92793da1a46a5f2a02a6f4c46c6496b28c43638adea8306fcb0caa1634f24e5"
 dependencies = [
  "heck 0.5.0",
  "proc-macro2",
@@ -531,9 +531,9 @@ dependencies = [
 
 [[package]]
 name = "find-msvc-tools"
-version = "0.1.8"
+version = "0.1.9"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "8591b0bcc8a98a64310a2fae1bb3e9b8564dd10e381e6e28010fde8e8e8568db"
+checksum = "5baebc0774151f905a1a2cc41989300b1e6fbb29aff0ceffa1064fdd3088d582"
 
 [[package]]
 name = "form_urlencoded"
@@ -778,12 +778,11 @@ dependencies = [
 
 [[package]]
 name = "hyper-util"
-version = "0.1.19"
+version = "0.1.20"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "727805d60e7938b76b826a6ef209eb70eaa1812794f9424d4a4e2d740662df5f"
+checksum = "96547c2556ec9d12fb1578c4eaf448b04993e7fb79cbaad930a656880a6bdfa0"
 dependencies = [
  "bytes",
- "futures-core",
  "http",
  "http-body",
  "hyper",
@@ -794,9 +793,9 @@ dependencies = [
 
 [[package]]
 name = "iana-time-zone"
-version = "0.1.64"
+version = "0.1.65"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "33e57f83510bb73707521ebaffa789ec8caf86f9657cad665b092b581d40e9fb"
+checksum = "e31bc9ad994ba00e440a8aa5c9ef0ec67d5cb5e5cb0cc7f8b744a35b389cc470"
 dependencies = [
  "android_system_properties",
  "core-foundation-sys",
@@ -953,7 +952,7 @@ checksum = "5e5032e24019045c762d3c0f28f5b6b8bbf38563a65908389bf7978758920897"
 
 [[package]]
 name = "logler-cli"
-version = "1.1.3"
+version = "1.2.0"
 dependencies = [
  "anyhow",
  "clap",
@@ -968,7 +967,7 @@ dependencies = [
 
 [[package]]
 name = "logler-core"
-version = "1.1.3"
+version = "1.2.0"
 dependencies = [
  "anyhow",
  "async-stream",
@@ -992,7 +991,7 @@ dependencies = [
 
 [[package]]
 name = "logler-py"
-version = "1.1.3"
+version = "1.2.0"
 dependencies = [
  "anyhow",
  "logler-core",
@@ -1004,7 +1003,7 @@ dependencies = [
 
 [[package]]
 name = "logler-server"
-version = "1.1.3"
+version = "1.2.0"
 dependencies = [
  "anyhow",
  "axum",
@@ -1217,9 +1216,9 @@ dependencies = [
 
 [[package]]
 name = "portable-atomic"
-version = "1.13.0"
+version = "1.13.1"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "f89776e4d69bb58bc6993e99ffa1d11f228b839984854c7daeb5d37f87cbe950"
+checksum = "c33a9471896f1c69cecef8d20cbe2f7accd12527ce60845ff44c153bb2a21b49"
 
 [[package]]
 name = "ppv-lite86"
@@ -1560,9 +1559,9 @@ dependencies = [
 
 [[package]]
 name = "slab"
-version = "0.4.11"
+version = "0.4.12"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "7a2ae44ef20feb57a68b23d846850f861394c2e02dc425a50098ae8c90267589"
+checksum = "0c790de23124f9ab44544d7ac05d60440adc586479ce501c1d6d7da3cd8c9cf5"
 
 [[package]]
 name = "smallvec"
@@ -2215,18 +2214,18 @@ checksum = "d7249219f66ced02969388cf2bb044a09756a083d0fab1e566056b04d9fbcaa5"
 
 [[package]]
 name = "zerocopy"
-version = "0.8.33"
+version = "0.8.37"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "668f5168d10b9ee831de31933dc111a459c97ec93225beb307aed970d1372dfd"
+checksum = "7456cf00f0685ad319c5b1693f291a650eaf345e941d082fc4e03df8a03996ac"
 dependencies = [
  "zerocopy-derive",
 ]
 
 [[package]]
 name = "zerocopy-derive"
-version = "0.8.33"
+version = "0.8.37"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "2c7962b26b0a8685668b671ee4b54d007a67d4eaf05fda79ac0ecf41e32270f1"
+checksum = "1328722bbf2115db7e19d69ebcc15e795719e2d66b60827c6a69a117365e37a0"
 dependencies = [
  "proc-macro2",
  "quote",
@@ -2235,6 +2234,6 @@ dependencies = [
 
 [[package]]
 name = "zmij"
-version = "1.0.16"
+version = "1.0.19"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "dfcd145825aace48cff44a8844de64bf75feec3080e0aa5cdbde72961ae51a65"
+checksum = "3ff05f8caa9038894637571ae6b9e29466c1f4f829d26c9b28f869a29cbe3445"

{logler-1.1.3 → logler-1.2.0}/Cargo.toml

@@ -3,7 +3,7 @@ members = ["crates/logler-py"]
 resolver = "2"
 
 [workspace.package]
-version = "1.1.3"
+version = "1.2.0"
 edition = "2021"
 authors = ["Logler Contributors"]
 license = "MIT"

{logler-1.1.3 → logler-1.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: logler
-Version: 1.1.3
+Version: 1.2.0
 Classifier: Development Status :: 4 - Beta
 Classifier: Intended Audience :: Developers
 Classifier: License :: OSI Approved :: MIT License
@@ -73,36 +73,25 @@ A modern, feature-rich log viewer that makes debugging a pleasure. View logs in
 - 🔍 **Semantic Search** - Find errors by description, not just exact matches
 - 🧵 **Thread Following** - Reconstruct request flows across distributed systems
 - 🌳 **Hierarchy Visualization** - Tree and waterfall views of nested operations, bottleneck detection
-- 📊 **Pattern Detection** - Automatically find repeated errors and cascading failures
 - 💾 **SQL Queries** - DuckDB-powered custom analysis for deep investigation
 - 📈 **Statistical Analysis** - Z-scores, percentiles, correlations, anomaly detection
+- 🌐 **OpenTelemetry Export** - Export traces to Jaeger, Zipkin, or OTLP collectors
 - 🌍 **Bilingual Docs** - Complete documentation in English and Japanese (日本語)
 
 ### 🚀 NEW: Advanced LLM Features
 
 **Designed specifically for AI agents with limited context windows:**
 
-- 💡 **Auto Insights** - `analyze_with_insights()` automatically detects patterns, errors, and suggests next steps
 - 📉 **Token-Efficient Output** - 44x token savings with summary/count/compact modes
 - 🔀 **Compare & Diff** - Compare successful vs failed requests, before/after deployments
 - 🌐 **Cross-Service Timeline** - Unified view across microservices for distributed debugging
 - 📝 **Investigation Sessions** - Track progress, undo/redo, save/resume investigations
 - 🎯 **Smart Sampling** - Representative sampling with multiple strategies (diverse, errors-focused, chronological)
 - 📄 **Report Generation** - Auto-generate markdown/text/JSON reports from investigation
-- 🤔 **Explain Feature** - Plain English explanations of cryptic errors with next steps
-- 💬 **Contextual Suggestions** - AI suggests what to investigate next based on findings
 
 ### Public API Contract
 
-Each code block carries a **Contract ID** (e.g., `[C01]`). The test suite in `tests/test_readme.py` executes these snippets against the documented public APIs. When this section changes, the tests must change with it — CI proves the README.
-
-#### [C01] Auto-insights analysis
-```python
-import logler.investigate as investigate
-
-result = investigate.analyze_with_insights(files=["app.log"])
-print(result['insights'])  # Automatic pattern detection, error analysis, suggestions
-```
+Each code block carries a **Contract ID** (e.g., `[C02]`). The test suite in `tests/test_readme.py` executes these snippets against the documented public APIs. When this section changes, the tests must change with it — CI proves the README.
 
 #### [C02] Token-efficient search
 ```python
@@ -141,7 +130,6 @@ import logler.investigate as investigate
 
 session = investigate.InvestigationSession(files=["app.log"], name="incident_2024")
 session.search(level="ERROR")
-session.find_patterns()
 session.add_note("Database connection pool exhausted")
 report = session.generate_report(format="markdown")  # Auto-generate report
 ```
@@ -157,14 +145,6 @@ sample = investigate.smart_sample(
 )
 ```
 
-#### [C07] Error explanation
-```python
-import logler.investigate as investigate
-
-explanation = investigate.explain(error_message="Connection pool exhausted", context="production")
-print(explanation)  # Common causes, next steps, production-specific advice
-```
-
 #### [C08] Thread hierarchy
 ```python
 import logler.investigate as investigate
@@ -198,7 +178,7 @@ print_waterfall(hierarchy, width=100)  # Waterfall timeline
 ```
 
 **📚 Complete LLM documentation:**
-- [LLM CLI Reference](docs/LLM_CLI_REFERENCE.md) - All 16 CLI commands for AI agents
+- [LLM CLI Reference](docs/LLM_CLI_REFERENCE.md) - All 17 CLI commands for AI agents
 - [Python API Guide](docs/LLM_README.md) - Library API and examples
 - [API Reference](docs/LLM_INVESTIGATION_API.md) - All investigation functions
 - [日本語ガイド](README.ja.md) - 完全なドキュメント
@@ -236,9 +216,7 @@ logler stats app.log --json      # JSON output
 
 **Investigate logs with smart analysis:**
 ```bash
-logler investigate app.log --auto-insights        # Auto-detect issues
 logler investigate app.log --errors               # Analyze errors
-logler investigate app.log --patterns             # Find repeated patterns
 logler investigate app.log --thread worker-1      # Follow specific thread
 logler investigate app.log --correlation req-123  # Follow correlation ID
 logler investigate app.log --trace trace-abc123   # Follow distributed trace
@@ -254,7 +232,7 @@ logler investigate app.log --thread worker-1 --hierarchy --max-depth 3   # Limit
 
 **LLM-first CLI (JSON output by default):**
 
-Designed for AI agents - 16 commands with structured JSON output, no truncation.
+Designed for AI agents - 17 commands with structured JSON output, no truncation.
 
 ```bash
 # Assessment & Overview
@@ -262,8 +240,13 @@ logler llm triage app.log --last 1h      # Quick severity assessment
 logler llm summarize app.log             # Concise summary with stats
 logler llm schema app.log                # Infer log structure
 
-# Search & Analysis
-logler llm search app.log --level ERROR  # Find entries (full results)
+# Discovery
+logler llm ids app.log                   # Find all thread/correlation/trace IDs
+
+# Search & Analysis (with filtering)
+logler llm search app.log --level ERROR,WARN --tail 20           # Last 20 errors/warnings
+logler llm search app.log --exclude-level DEBUG --service api    # Filter by service
+logler llm search app.log --exclude-query "health" --max-bytes 4000  # Budget-controlled
 logler llm sql "SELECT level, COUNT(*) FROM logs GROUP BY level" -f app.log
 
 # Request Tracing
@@ -281,7 +264,7 @@ logler llm context app.log 1523 --before 10 --after 10
 logler llm export trace-xyz --format jaeger
 ```
 
-See **[LLM CLI Reference](docs/LLM_CLI_REFERENCE.md)** for complete documentation of all 16 commands.
+See **[LLM CLI Reference](docs/LLM_CLI_REFERENCE.md)** for complete documentation of all 17 commands.
 
 ### Visualization Modes
 
@@ -385,25 +368,20 @@ logler stats app.log --json | jq '.by_level'
 ### Investigation & Analysis
 
 ```bash
-# Auto-detect issues with insights
-logler investigate app.log --auto-insights
-# Output: Automatic error analysis, pattern detection, actionable suggestions
-
 # Analyze errors with context
 logler investigate app.log --errors
 # Shows error frequency, top error messages, time ranges
 
-# Find repeated patterns
-logler investigate app.log --patterns --min-occurrences 5
-# Identifies logs that repeat 5+ times
-
 # Follow a specific thread or request
 logler investigate app.log --thread worker-1
 logler investigate app.log --correlation req-abc123
 logler investigate app.log --trace trace-xyz789
 
+# Build hierarchy tree with bottleneck detection
+logler investigate app.log --correlation req-123 --hierarchy
+
 # Token-efficient output for LLMs
-logler investigate app.log --auto-insights --output summary
+logler investigate app.log --errors --output summary
 # Returns aggregated statistics instead of full logs
 
 # JSON output for automation
@@ -465,7 +443,7 @@ To unlock **all** of logler's capabilities (especially multi-level thread hierar
 |-------|---------|---------|
 | `timestamp` | When the event occurred (ISO 8601) | Timeline, duration analysis |
 | `level` | Log level (DEBUG/INFO/WARN/ERROR/FATAL) | Filtering, error detection |
-| `message` | Human-readable description | Search, pattern detection |
+| `message` | Human-readable description | Search, filtering |
 | `thread_id` | Thread/worker identifier | Thread grouping, timeline |
 | `correlation_id` | Request ID across services | Cross-service tracing |
 | `trace_id` | Distributed trace identifier | OpenTelemetry integration |
@@ -577,10 +555,36 @@ Built with:
 
 1. **Use `--follow` mode** for real-time debugging
 2. **Filter by thread** to trace execution flow
-3. **Use `--auto-insights`** for automatic issue detection
+3. **Use `--hierarchy`** to visualize request flow with bottleneck detection
 4. **Export stats as JSON** for automation
 5. **Watch directories** for new log files
 
+## 🎓 Interactive Tours
+
+Learn logler hands-on with [marimo](https://marimo.io/) notebook tours. Each tour is self-contained with sample data -- no external files needed.
+
+```bash
+# Run any tour in your browser
+uv run marimo edit examples/tours/tour_01_fundamentals.py
+```
+
+| Tour | Topic |
+|------|-------|
+| 01 | Fundamentals -- search, filter, output formats |
+| 02 | Thread Tracking -- grouping, correlation IDs |
+| 03 | Hierarchy -- tree views, waterfall, bottleneck detection |
+| 04 | Investigation -- sessions, history, report generation |
+| 06 | Flamegraph -- performance visualization |
+| 07 | Error Flow -- root cause analysis, propagation chains |
+| 08 | Comparison -- diff hierarchies, compare threads |
+| 09 | Tracing Exports -- Jaeger and Zipkin formats |
+| 10 | Sampling -- smart sampling strategies |
+| 12 | Multi-File -- cross-service distributed tracing |
+| 13 | Live Watching -- real-time tailing and streaming |
+| 14 | Performance -- 10K+ entries, benchmarks |
+
+See the [examples README](examples/README.md) for the full learning path.
+
 ## 🎓 Examples
 
 ### Debug a specific request
@@ -602,10 +606,10 @@ logler view app.log -f --level ERROR
 logler view app.log --thread worker-1
 ```
 
-### Investigate with insights
+### Build request hierarchy
 ```bash
-logler investigate app.log --auto-insights
-# Automatic pattern detection and issue analysis
+logler investigate app.log --correlation req-123 --hierarchy
+# Visualize request flow with bottleneck detection
 ```
 
 ---

{logler-1.1.3 → logler-1.2.0}/README.md

@@ -35,36 +35,25 @@ A modern, feature-rich log viewer that makes debugging a pleasure. View logs in
 - 🔍 **Semantic Search** - Find errors by description, not just exact matches
 - 🧵 **Thread Following** - Reconstruct request flows across distributed systems
 - 🌳 **Hierarchy Visualization** - Tree and waterfall views of nested operations, bottleneck detection
-- 📊 **Pattern Detection** - Automatically find repeated errors and cascading failures
 - 💾 **SQL Queries** - DuckDB-powered custom analysis for deep investigation
 - 📈 **Statistical Analysis** - Z-scores, percentiles, correlations, anomaly detection
+- 🌐 **OpenTelemetry Export** - Export traces to Jaeger, Zipkin, or OTLP collectors
 - 🌍 **Bilingual Docs** - Complete documentation in English and Japanese (日本語)
 
 ### 🚀 NEW: Advanced LLM Features
 
 **Designed specifically for AI agents with limited context windows:**
 
-- 💡 **Auto Insights** - `analyze_with_insights()` automatically detects patterns, errors, and suggests next steps
 - 📉 **Token-Efficient Output** - 44x token savings with summary/count/compact modes
 - 🔀 **Compare & Diff** - Compare successful vs failed requests, before/after deployments
 - 🌐 **Cross-Service Timeline** - Unified view across microservices for distributed debugging
 - 📝 **Investigation Sessions** - Track progress, undo/redo, save/resume investigations
 - 🎯 **Smart Sampling** - Representative sampling with multiple strategies (diverse, errors-focused, chronological)
 - 📄 **Report Generation** - Auto-generate markdown/text/JSON reports from investigation
-- 🤔 **Explain Feature** - Plain English explanations of cryptic errors with next steps
-- 💬 **Contextual Suggestions** - AI suggests what to investigate next based on findings
 
 ### Public API Contract
 
-Each code block carries a **Contract ID** (e.g., `[C01]`). The test suite in `tests/test_readme.py` executes these snippets against the documented public APIs. When this section changes, the tests must change with it — CI proves the README.
-
-#### [C01] Auto-insights analysis
-```python
-import logler.investigate as investigate
-
-result = investigate.analyze_with_insights(files=["app.log"])
-print(result['insights'])  # Automatic pattern detection, error analysis, suggestions
-```
+Each code block carries a **Contract ID** (e.g., `[C02]`). The test suite in `tests/test_readme.py` executes these snippets against the documented public APIs. When this section changes, the tests must change with it — CI proves the README.
 
 #### [C02] Token-efficient search
 ```python
@@ -103,7 +92,6 @@ import logler.investigate as investigate
 
 session = investigate.InvestigationSession(files=["app.log"], name="incident_2024")
 session.search(level="ERROR")
-session.find_patterns()
 session.add_note("Database connection pool exhausted")
 report = session.generate_report(format="markdown")  # Auto-generate report
 ```
@@ -119,14 +107,6 @@ sample = investigate.smart_sample(
 )
 ```
 
-#### [C07] Error explanation
-```python
-import logler.investigate as investigate
-
-explanation = investigate.explain(error_message="Connection pool exhausted", context="production")
-print(explanation)  # Common causes, next steps, production-specific advice
-```
-
 #### [C08] Thread hierarchy
 ```python
 import logler.investigate as investigate
@@ -160,7 +140,7 @@ print_waterfall(hierarchy, width=100)  # Waterfall timeline
 ```
 
 **📚 Complete LLM documentation:**
-- [LLM CLI Reference](docs/LLM_CLI_REFERENCE.md) - All 16 CLI commands for AI agents
+- [LLM CLI Reference](docs/LLM_CLI_REFERENCE.md) - All 17 CLI commands for AI agents
 - [Python API Guide](docs/LLM_README.md) - Library API and examples
 - [API Reference](docs/LLM_INVESTIGATION_API.md) - All investigation functions
 - [日本語ガイド](README.ja.md) - 完全なドキュメント
@@ -198,9 +178,7 @@ logler stats app.log --json      # JSON output
 
 **Investigate logs with smart analysis:**
 ```bash
-logler investigate app.log --auto-insights        # Auto-detect issues
 logler investigate app.log --errors               # Analyze errors
-logler investigate app.log --patterns             # Find repeated patterns
 logler investigate app.log --thread worker-1      # Follow specific thread
 logler investigate app.log --correlation req-123  # Follow correlation ID
 logler investigate app.log --trace trace-abc123   # Follow distributed trace
@@ -216,7 +194,7 @@ logler investigate app.log --thread worker-1 --hierarchy --max-depth 3   # Limit
 
 **LLM-first CLI (JSON output by default):**
 
-Designed for AI agents - 16 commands with structured JSON output, no truncation.
+Designed for AI agents - 17 commands with structured JSON output, no truncation.
 
 ```bash
 # Assessment & Overview
@@ -224,8 +202,13 @@ logler llm triage app.log --last 1h      # Quick severity assessment
 logler llm summarize app.log             # Concise summary with stats
 logler llm schema app.log                # Infer log structure
 
-# Search & Analysis
-logler llm search app.log --level ERROR  # Find entries (full results)
+# Discovery
+logler llm ids app.log                   # Find all thread/correlation/trace IDs
+
+# Search & Analysis (with filtering)
+logler llm search app.log --level ERROR,WARN --tail 20           # Last 20 errors/warnings
+logler llm search app.log --exclude-level DEBUG --service api    # Filter by service
+logler llm search app.log --exclude-query "health" --max-bytes 4000  # Budget-controlled
 logler llm sql "SELECT level, COUNT(*) FROM logs GROUP BY level" -f app.log
 
 # Request Tracing
@@ -243,7 +226,7 @@ logler llm context app.log 1523 --before 10 --after 10
 logler llm export trace-xyz --format jaeger
 ```
 
-See **[LLM CLI Reference](docs/LLM_CLI_REFERENCE.md)** for complete documentation of all 16 commands.
+See **[LLM CLI Reference](docs/LLM_CLI_REFERENCE.md)** for complete documentation of all 17 commands.
 
 ### Visualization Modes
 
@@ -347,25 +330,20 @@ logler stats app.log --json | jq '.by_level'
 ### Investigation & Analysis
 
 ```bash
-# Auto-detect issues with insights
-logler investigate app.log --auto-insights
-# Output: Automatic error analysis, pattern detection, actionable suggestions
-
 # Analyze errors with context
 logler investigate app.log --errors
 # Shows error frequency, top error messages, time ranges
 
-# Find repeated patterns
-logler investigate app.log --patterns --min-occurrences 5
-# Identifies logs that repeat 5+ times
-
 # Follow a specific thread or request
 logler investigate app.log --thread worker-1
 logler investigate app.log --correlation req-abc123
 logler investigate app.log --trace trace-xyz789
 
+# Build hierarchy tree with bottleneck detection
+logler investigate app.log --correlation req-123 --hierarchy
+
 # Token-efficient output for LLMs
-logler investigate app.log --auto-insights --output summary
+logler investigate app.log --errors --output summary
 # Returns aggregated statistics instead of full logs
 
 # JSON output for automation
@@ -427,7 +405,7 @@ To unlock **all** of logler's capabilities (especially multi-level thread hierar
 |-------|---------|---------|
 | `timestamp` | When the event occurred (ISO 8601) | Timeline, duration analysis |
 | `level` | Log level (DEBUG/INFO/WARN/ERROR/FATAL) | Filtering, error detection |
-| `message` | Human-readable description | Search, pattern detection |
+| `message` | Human-readable description | Search, filtering |
 | `thread_id` | Thread/worker identifier | Thread grouping, timeline |
 | `correlation_id` | Request ID across services | Cross-service tracing |
 | `trace_id` | Distributed trace identifier | OpenTelemetry integration |
@@ -539,10 +517,36 @@ Built with:
 
 1. **Use `--follow` mode** for real-time debugging
 2. **Filter by thread** to trace execution flow
-3. **Use `--auto-insights`** for automatic issue detection
+3. **Use `--hierarchy`** to visualize request flow with bottleneck detection
 4. **Export stats as JSON** for automation
 5. **Watch directories** for new log files
 
+## 🎓 Interactive Tours
+
+Learn logler hands-on with [marimo](https://marimo.io/) notebook tours. Each tour is self-contained with sample data -- no external files needed.
+
+```bash
+# Run any tour in your browser
+uv run marimo edit examples/tours/tour_01_fundamentals.py
+```
+
+| Tour | Topic |
+|------|-------|
+| 01 | Fundamentals -- search, filter, output formats |
+| 02 | Thread Tracking -- grouping, correlation IDs |
+| 03 | Hierarchy -- tree views, waterfall, bottleneck detection |
+| 04 | Investigation -- sessions, history, report generation |
+| 06 | Flamegraph -- performance visualization |
+| 07 | Error Flow -- root cause analysis, propagation chains |
+| 08 | Comparison -- diff hierarchies, compare threads |
+| 09 | Tracing Exports -- Jaeger and Zipkin formats |
+| 10 | Sampling -- smart sampling strategies |
+| 12 | Multi-File -- cross-service distributed tracing |
+| 13 | Live Watching -- real-time tailing and streaming |
+| 14 | Performance -- 10K+ entries, benchmarks |
+
+See the [examples README](examples/README.md) for the full learning path.
+
 ## 🎓 Examples
 
 ### Debug a specific request
@@ -564,10 +568,10 @@ logler view app.log -f --level ERROR
 logler view app.log --thread worker-1
 ```
 
-### Investigate with insights
+### Build request hierarchy
 ```bash
-logler investigate app.log --auto-insights
-# Automatic pattern detection and issue analysis
+logler investigate app.log --correlation req-123 --hierarchy
+# Visualize request flow with bottleneck detection
 ```
 
 ---