logler 1.1.2__tar.gz → 1.1.3__tar.gz

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

@@ -253,9 +253,9 @@ checksum = "37b2a672a2cb129a2e41c10b1224bb368f9f37a2b16b612598138befd7b37eb5"
 
 [[package]]
 name = "cc"
-version = "1.2.53"
+version = "1.2.54"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "755d2fce177175ffca841e9a06afdb2c4ab0f593d53b4dee48147dfaade85932"
+checksum = "6354c81bbfd62d9cfa9cb3c773c2b7b2a3a482d569de977fd0e961f6e7c00583"
 dependencies = [
  "find-msvc-tools",
  "shlex",
@@ -953,7 +953,7 @@ checksum = "5e5032e24019045c762d3c0f28f5b6b8bbf38563a65908389bf7978758920897"
 
 [[package]]
 name = "logler-cli"
-version = "1.1.2"
+version = "1.1.3"
 dependencies = [
  "anyhow",
  "clap",
@@ -968,7 +968,7 @@ dependencies = [
 
 [[package]]
 name = "logler-core"
-version = "1.1.2"
+version = "1.1.3"
 dependencies = [
  "anyhow",
  "async-stream",
@@ -992,7 +992,7 @@ dependencies = [
 
 [[package]]
 name = "logler-py"
-version = "1.1.2"
+version = "1.1.3"
 dependencies = [
  "anyhow",
  "logler-core",
@@ -1004,7 +1004,7 @@ dependencies = [
 
 [[package]]
 name = "logler-server"
-version = "1.1.2"
+version = "1.1.3"
 dependencies = [
  "anyhow",
  "axum",
@@ -1306,9 +1306,9 @@ dependencies = [
 
 [[package]]
 name = "quote"
-version = "1.0.43"
+version = "1.0.44"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "dc74d9a594b72ae6656596548f56f667211f8a97b3d4c3d467150794690dc40a"
+checksum = "21b2ebcf727b7760c461f091f9f0f539b77b8e87f2fd88131e7f1b433b3cece4"
 dependencies = [
  "proc-macro2",
 ]
@@ -1572,9 +1572,9 @@ checksum = "67b1b7a3b5fe4f1376887184045fcf45c69e92af734b7aaddc05fb777b6fbd03"
 
 [[package]]
 name = "socket2"
-version = "0.6.1"
+version = "0.6.2"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "17129e116933cf371d018bb80ae557e889637989d8638274fb25622827b03881"
+checksum = "86f4aa3ad99f2088c990dfa82d367e19cb29268ed67c574d10d0a4bfe71f07e0"
 dependencies = [
  "libc",
  "windows-sys 0.60.2",
@@ -1888,9 +1888,9 @@ checksum = "06abde3611657adf66d383f00b093d7faecc7fa57071cce2578660c9f1010821"
 
 [[package]]
 name = "uuid"
-version = "1.19.0"
+version = "1.20.0"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "e2e054861b4bd027cd373e18e8d8d8e6548085000e41290d95ce0c373a654b4a"
+checksum = "ee48d38b119b0cd71fe4141b30f5ba9c7c5d9f4e7a3a8b4a674e4b6ef789976f"
 dependencies = [
  "getrandom 0.3.4",
  "js-sys",

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

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

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

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: logler
-Version: 1.1.2
+Version: 1.1.3
 Classifier: Development Status :: 4 - Beta
 Classifier: Intended Audience :: Developers
 Classifier: License :: OSI Approved :: MIT License
@@ -92,75 +92,116 @@ A modern, feature-rich log viewer that makes debugging a pleasure. View logs in
 - 🤔 **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
 
-# 🎯 One-line auto investigation with insights
 result = investigate.analyze_with_insights(files=["app.log"])
 print(result['insights'])  # Automatic pattern detection, error analysis, suggestions
+```
+
+#### [C02] Token-efficient search
+```python
+import logler.investigate as investigate
 
-# 📉 Token-efficient search (44x smaller output)
 errors = investigate.search(files=["app.log"], level="ERROR", output_format="summary")
 # Returns aggregated stats instead of all entries - perfect for limited context windows
+```
+
+#### [C03] Compare threads
+```python
+import logler.investigate as investigate
 
-# 🔀 Compare successful vs failed requests
 diff = investigate.compare_threads(
     files=["app.log"],
     correlation_a="req-success-123",
     correlation_b="req-failed-456"
 )
-print(diff['summary'])  # "Thread B took 2341ms longer and had 5 errors (cache miss, timeout)"
+print(diff['summary'])  # Comparison of two request flows
+```
+
+#### [C04] Cross-service timeline
+```python
+import logler.investigate as investigate
 
-# 🌐 Cross-service distributed tracing
 timeline = investigate.cross_service_timeline(
     files={"api": ["api.log"], "db": ["db.log"], "cache": ["cache.log"]},
     correlation_id="req-12345"
 )
 # See request flow: API → DB → Cache with latency breakdown
+```
+
+#### [C05] Investigation sessions
+```python
+import logler.investigate as investigate
 
-# 📝 Track investigation with sessions
 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
+```
+
+#### [C06] Smart sampling
+```python
+import logler.investigate as investigate
 
-# 🎯 Smart sampling (representative sample of huge logs)
 sample = investigate.smart_sample(
     files=["huge.log"],
     strategy="errors_focused",  # or "diverse", "representative", "chronological"
     sample_size=50
 )
+```
+
+#### [C07] Error explanation
+```python
+import logler.investigate as investigate
 
-# 🤔 Explain cryptic errors in plain English
 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
 
-# 🌳 Hierarchical thread visualization (NEW!)
 hierarchy = investigate.follow_thread_hierarchy(
     files=["app.log"],
     root_identifier="req-123",
     min_confidence=0.8  # Only show high-confidence relationships
 )
-
 # Automatic bottleneck detection
-if hierarchy['bottleneck']:
+if hierarchy.get('bottleneck'):
     print(f"Bottleneck: {hierarchy['bottleneck']['node_id']} took {hierarchy['bottleneck']['duration_ms']}ms")
+```
+
+#### [C09] Hierarchy summary
+```python
+import logler.investigate as investigate
 
-# Get summary
+# Using hierarchy from [C08]
 summary = investigate.get_hierarchy_summary(hierarchy)
 print(summary)  # Shows tree structure, errors, bottlenecks
+```
 
-# Visualize in CLI
+#### [C10] Tree visualization
+```python
 from logler.tree_formatter import print_tree, print_waterfall
+
+# Using hierarchy from [C08]
 print_tree(hierarchy, mode="detailed", show_duration=True)
-print_waterfall(hierarchy, width=100)  # Waterfall timeline showing parallel operations
+print_waterfall(hierarchy, width=100)  # Waterfall timeline
 ```
 
 **📚 Complete LLM documentation:**
-- [English Guide](docs/LLM_README.md) - Complete API and examples
+- [LLM CLI Reference](docs/LLM_CLI_REFERENCE.md) - All 16 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) - 完全なドキュメント
-- [API Reference](docs/LLM_INVESTIGATION_API.md) - All investigation tools
 - [Examples](examples/) - Production incident investigations
 
 ## 🚀 Quick Start
@@ -200,16 +241,48 @@ 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
 logler investigate app.log --output summary       # Token-efficient output
 
 # 🌳 NEW: Hierarchical Thread Visualization
 logler investigate app.log --correlation req-123 --hierarchy         # Show thread hierarchy tree
-logler investigate app.log --correlation trace-abc123 --hierarchy --waterfall  # Show waterfall timeline
+logler investigate app.log --trace trace-abc123 --hierarchy --waterfall        # Show waterfall timeline
 logler investigate app.log --correlation req-123 --hierarchy --flamegraph # Show flamegraph view
 logler investigate app.log --hierarchy --show-error-flow             # Analyze error propagation
 logler investigate app.log --thread worker-1 --hierarchy --max-depth 3   # Limit hierarchy depth
 ```
 
+**LLM-first CLI (JSON output by default):**
+
+Designed for AI agents - 16 commands with structured JSON output, no truncation.
+
+```bash
+# Assessment & Overview
+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)
+logler llm sql "SELECT level, COUNT(*) FROM logs GROUP BY level" -f app.log
+
+# Request Tracing
+logler llm correlate req-123 --files "*.log"   # Follow correlation ID
+logler llm hierarchy trace-xyz --files "*.log"  # Build hierarchy tree
+logler llm bottleneck trace-xyz --files "*.log" # Find slow operations
+
+# Comparison
+logler llm compare req-fail req-success --files "*.log"  # Compare requests
+logler llm diff app.log --baseline 1h                    # Before/after analysis
+
+# Utilities
+logler llm sample app.log --strategy errors_focused --size 50
+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.
+
 ### Visualization Modes
 
 **Tree View** - Shows parent-child relationships:
@@ -327,6 +400,7 @@ logler investigate app.log --patterns --min-occurrences 5
 # 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
 
 # Token-efficient output for LLMs
 logler investigate app.log --auto-insights --output summary
@@ -437,6 +511,9 @@ Track requests across services:
 # Follow a specific correlation ID
 logler investigate app.log --correlation req-12345
 
+# Follow a distributed trace ID
+logler investigate app.log --trace trace-xyz789
+
 # View across multiple service logs
 logler view app.log service.log --grep "req-12345"
 ```

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

@@ -54,75 +54,116 @@ A modern, feature-rich log viewer that makes debugging a pleasure. View logs in
 - 🤔 **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
 
-# 🎯 One-line auto investigation with insights
 result = investigate.analyze_with_insights(files=["app.log"])
 print(result['insights'])  # Automatic pattern detection, error analysis, suggestions
+```
+
+#### [C02] Token-efficient search
+```python
+import logler.investigate as investigate
 
-# 📉 Token-efficient search (44x smaller output)
 errors = investigate.search(files=["app.log"], level="ERROR", output_format="summary")
 # Returns aggregated stats instead of all entries - perfect for limited context windows
+```
+
+#### [C03] Compare threads
+```python
+import logler.investigate as investigate
 
-# 🔀 Compare successful vs failed requests
 diff = investigate.compare_threads(
     files=["app.log"],
     correlation_a="req-success-123",
     correlation_b="req-failed-456"
 )
-print(diff['summary'])  # "Thread B took 2341ms longer and had 5 errors (cache miss, timeout)"
+print(diff['summary'])  # Comparison of two request flows
+```
+
+#### [C04] Cross-service timeline
+```python
+import logler.investigate as investigate
 
-# 🌐 Cross-service distributed tracing
 timeline = investigate.cross_service_timeline(
     files={"api": ["api.log"], "db": ["db.log"], "cache": ["cache.log"]},
     correlation_id="req-12345"
 )
 # See request flow: API → DB → Cache with latency breakdown
+```
+
+#### [C05] Investigation sessions
+```python
+import logler.investigate as investigate
 
-# 📝 Track investigation with sessions
 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
+```
+
+#### [C06] Smart sampling
+```python
+import logler.investigate as investigate
 
-# 🎯 Smart sampling (representative sample of huge logs)
 sample = investigate.smart_sample(
     files=["huge.log"],
     strategy="errors_focused",  # or "diverse", "representative", "chronological"
     sample_size=50
 )
+```
+
+#### [C07] Error explanation
+```python
+import logler.investigate as investigate
 
-# 🤔 Explain cryptic errors in plain English
 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
 
-# 🌳 Hierarchical thread visualization (NEW!)
 hierarchy = investigate.follow_thread_hierarchy(
     files=["app.log"],
     root_identifier="req-123",
     min_confidence=0.8  # Only show high-confidence relationships
 )
-
 # Automatic bottleneck detection
-if hierarchy['bottleneck']:
+if hierarchy.get('bottleneck'):
     print(f"Bottleneck: {hierarchy['bottleneck']['node_id']} took {hierarchy['bottleneck']['duration_ms']}ms")
+```
+
+#### [C09] Hierarchy summary
+```python
+import logler.investigate as investigate
 
-# Get summary
+# Using hierarchy from [C08]
 summary = investigate.get_hierarchy_summary(hierarchy)
 print(summary)  # Shows tree structure, errors, bottlenecks
+```
 
-# Visualize in CLI
+#### [C10] Tree visualization
+```python
 from logler.tree_formatter import print_tree, print_waterfall
+
+# Using hierarchy from [C08]
 print_tree(hierarchy, mode="detailed", show_duration=True)
-print_waterfall(hierarchy, width=100)  # Waterfall timeline showing parallel operations
+print_waterfall(hierarchy, width=100)  # Waterfall timeline
 ```
 
 **📚 Complete LLM documentation:**
-- [English Guide](docs/LLM_README.md) - Complete API and examples
+- [LLM CLI Reference](docs/LLM_CLI_REFERENCE.md) - All 16 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) - 完全なドキュメント
-- [API Reference](docs/LLM_INVESTIGATION_API.md) - All investigation tools
 - [Examples](examples/) - Production incident investigations
 
 ## 🚀 Quick Start
@@ -162,16 +203,48 @@ 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
 logler investigate app.log --output summary       # Token-efficient output
 
 # 🌳 NEW: Hierarchical Thread Visualization
 logler investigate app.log --correlation req-123 --hierarchy         # Show thread hierarchy tree
-logler investigate app.log --correlation trace-abc123 --hierarchy --waterfall  # Show waterfall timeline
+logler investigate app.log --trace trace-abc123 --hierarchy --waterfall        # Show waterfall timeline
 logler investigate app.log --correlation req-123 --hierarchy --flamegraph # Show flamegraph view
 logler investigate app.log --hierarchy --show-error-flow             # Analyze error propagation
 logler investigate app.log --thread worker-1 --hierarchy --max-depth 3   # Limit hierarchy depth
 ```
 
+**LLM-first CLI (JSON output by default):**
+
+Designed for AI agents - 16 commands with structured JSON output, no truncation.
+
+```bash
+# Assessment & Overview
+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)
+logler llm sql "SELECT level, COUNT(*) FROM logs GROUP BY level" -f app.log
+
+# Request Tracing
+logler llm correlate req-123 --files "*.log"   # Follow correlation ID
+logler llm hierarchy trace-xyz --files "*.log"  # Build hierarchy tree
+logler llm bottleneck trace-xyz --files "*.log" # Find slow operations
+
+# Comparison
+logler llm compare req-fail req-success --files "*.log"  # Compare requests
+logler llm diff app.log --baseline 1h                    # Before/after analysis
+
+# Utilities
+logler llm sample app.log --strategy errors_focused --size 50
+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.
+
 ### Visualization Modes
 
 **Tree View** - Shows parent-child relationships:
@@ -289,6 +362,7 @@ logler investigate app.log --patterns --min-occurrences 5
 # 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
 
 # Token-efficient output for LLMs
 logler investigate app.log --auto-insights --output summary
@@ -399,6 +473,9 @@ Track requests across services:
 # Follow a specific correlation ID
 logler investigate app.log --correlation req-12345
 
+# Follow a distributed trace ID
+logler investigate app.log --trace trace-xyz789
+
 # View across multiple service logs
 logler view app.log service.log --grep "req-12345"
 ```