log tailing

Author: clavery

docs/cli/mrt.md

@@ -19,6 +19,7 @@ Commands for managing Managed Runtime (MRT) projects, environments, and bundles
 | `mrt env redirect` | `list`, `create`, `delete`, `clone` | Manage URL redirects |
 | `mrt env access-control` | `list` | Manage access control headers |
 | `mrt bundle` | `deploy`, `list`, `history`, `download` | Manage bundles and deployments |
+| `mrt tail-logs` | | Tail real-time application logs |
 | `mrt user` | `profile`, `api-key`, `email-prefs` | Manage user settings |
 
 ## Global MRT Flags
@@ -506,6 +507,38 @@ b2c mrt bundle download 12345 -p my-storefront --url-only
 
 ---
 
+## Tail Logs
+
+### b2c mrt tail-logs
+
+Tail application logs from a Managed Runtime environment in real time. Connects via WebSocket and streams log entries until interrupted with Ctrl+C.
+
+```bash
+# Tail all logs
+b2c mrt tail-logs -p my-storefront -e staging
+
+# Filter by log level
+b2c mrt tail-logs -p my-storefront -e production --level ERROR --level WARN
+
+# Search with regex pattern
+b2c mrt tail-logs -p my-storefront -e staging --search "timeout"
+
+# Search with OR pattern
+b2c mrt tail-logs -p my-storefront -e staging --search "GET|POST"
+
+# Output as JSON
+b2c mrt tail-logs -p my-storefront -e staging --json
+```
+
+**Flags:**
+| Flag | Description |
+|------|-------------|
+| `--level` | Filter by log level (ERROR, WARN, INFO, DEBUG, etc.). Repeatable for multiple levels. |
+| `--search`, `-g` | Filter entries matching a regex pattern (case-insensitive) |
+| `--no-color` | Disable colored output |
+
+---
+
 ## User Commands
 
 ### b2c mrt user profile

docs/guide/storefront-next.md

@@ -158,6 +158,23 @@ b2c mrt bundle deploy -p <PROJECT> -e <ENVIRONMENT> \
 
 These patterns match the defaults used by `pnpm sfnext push`. The `--ssr-only` and `--ssr-shared` flags accept either a JSON array (for patterns with brace expansion) or a comma-separated string, and can be overridden if your project structure differs.
 
+## Step 6: Debugging with Log Tailing
+
+After deploying, you can tail application logs in real time to debug runtime issues.
+
+```bash
+# Tail all logs from your environment
+b2c mrt tail-logs -p <PROJECT> -e <ENVIRONMENT>
+
+# Show only errors and warnings
+b2c mrt tail-logs -p <PROJECT> -e <ENVIRONMENT> --level ERROR --level WARN
+
+# Search for specific patterns
+b2c mrt tail-logs -p <PROJECT> -e <ENVIRONMENT> --search "timeout|500"
+```
+
+This is useful for diagnosing deployment failures, SSR errors, and API connectivity issues. See [MRT Commands](/cli/mrt#tail-logs) for all options.
+
 ## Summary
 
 | Step | Command | Required? |
@@ -167,6 +184,7 @@ These patterns match the defaults used by `pnpm sfnext push`. The `--ssr-only` a
 | 3. Create MRT Environment | `b2c mrt env create` | Yes |
 | 4. Set Environment Variables | `b2c mrt env var set` | Yes |
 | 5. Deploy | `pnpm sfnext push` or `b2c mrt bundle deploy` | Yes |
+| 6. Debug with Log Tailing | `b2c mrt tail-logs` | Optional |
 
 ## Next Steps