@tsuga/cli 1.0.6 → 1.0.8

package/README.md

@@ -43,6 +43,33 @@ Show current configuration:
 tsuga config
 ```
 
+## Clusters
+
+If your tenant has multiple clusters, you can target a specific one:
+
+```bash
+# List clusters
+tsuga cluster list
+
+# Save the cluster you want to use by default
+tsuga cluster use <cluster-id>
+
+# Clear the saved cluster
+tsuga cluster reset
+```
+
+You can also override the cluster per-command:
+
+```bash
+# Environment variable
+export TSUGA_CLUSTER_ID=<cluster-id>
+
+# CLI flag (highest priority)
+tsuga --cluster <cluster-id> logs search
+```
+
+Priority order: `--cluster` flag → `TSUGA_CLUSTER_ID` env var → saved config. If unset, the backend falls back to the first cluster.
+
 ## Defaults
 
 Telemetry commands have built-in defaults so you can omit common flags:
@@ -100,9 +127,13 @@ tsuga teams create -d '{"name": "Platform", "visibility": "public"}'
 
 ### Available resources
 
-`dashboards`, `ingestion-api-keys`, `monitors`, `notification-rules`, `notification-silences`, `retention-policies`, `routes`, `services`, `tag-policies`, `teams`
+`cloud-resources`, `dashboards`, `ingestion-api-keys`, `monitors`, `notification-rules`, `notification-silences`, `quality-reports`, `retention-policies`, `routes`, `services`, `tag-policies`, `teams`
 
-> Note: `ingestion-api-keys` does not support `get <id>`.
+> Notes:
+>
+> - `ingestion-api-keys` does not support `get <id>`.
+> - `services` is read-only (`list`, `get`).
+> - `cloud-resources` and `quality-reports` are read-only and only support `list`.
 
 ### Generating a request skeleton
 
@@ -166,6 +197,35 @@ tsuga logs search --from -1h --query 'level:ERROR'
 tsuga logs search --from 1704067200 --to 1704153600 --query 'service:api'
 ```
 
+By default, the full JSON response is printed. Use `--fields` to project specific
+dot-paths from each log, and `-o tsv|csv` for tabular output:
+
+```bash
+# JSON projected to selected fields (preserves the {logs: [...]} envelope and nesting)
+tsuga logs search --from -10m \
+  --fields timestamp,level,message,context.k8s.pod.name
+
+# TSV with default columns: timestamp, level, message
+tsuga logs search --from -10m --query 'level:ERROR' -o tsv
+
+# CSV with custom columns
+tsuga logs search --from -10m -o csv \
+  --fields timestamp,level,message,context.k8s.pod.name
+```
+
+### Log patterns
+
+```bash
+# Group recent logs into patterns
+tsuga logs patterns --from -1h --query 'level:ERROR'
+
+# List new error patterns observed in the time range
+tsuga logs new-error-patterns --from -24h --team my-team --service api --env prod
+
+# List error patterns whose volume increased for a team
+tsuga logs error-pattern-increases --from -24h --team my-team --env prod
+```
+
 ### Search traces
 
 ```bash
@@ -197,9 +257,26 @@ Use `--generate-skeleton` to get a template:
 tsuga aggregation scalar --generate-skeleton > query.json
 ```
 
+## Service graph
+
+Inspect service dependency graphs:
+
+```bash
+tsuga service-graph get <service-id> --from -1h --query 'env:prod'
+```
+
+## Documentation
+
+Browse and search the Tsuga documentation:
+
+```bash
+tsuga docs search 'log routes'
+tsuga docs get getting-started/send-your-first-logs
+```
+
 ## Tips
 
-Output is always JSON, so you can pipe to `jq`:
+Default output is JSON, so you can pipe to `jq`:
 
 ```bash
 tsuga dashboards list | jq '.[].name'