@tsuga/cli 1.1.1 → 1.3.0

package/README.md

@@ -55,7 +55,7 @@ All authentication lives under `tsuga auth`.
 For interactive use, log in as a user with a browser authorization flow:
 
 ```bash
-# Prints an authorization URL. On macOS, also opens it in your browser.
+# Opens your browser to an authorization URL, or prints the URL if it can't be opened.
 tsuga auth login
 
 # Print the saved user access token
@@ -193,7 +193,7 @@ tsuga logs patterns --rationale "exploring telemetry to investigate prod outage"
 
 ### Available resources
 
-`cloud-resources`, `dashboards`, `ingestion-api-keys`, `investigations`, `monitors`, `notification-rules`, `notification-silences`, `quality-reports`, `retention-policies`, `routes`, `services`, `tag-policies`, `teams`
+`cloud-resources`, `dashboards`, `ingestion-api-keys`, `investigations`, `monitors`, `notification-rules`, `notification-silences`, `quality-reports`, `retention-policies`, `routes`, `services`, `slos`, `tag-policies`, `teams`
 
 > Notes:
 >
@@ -307,6 +307,30 @@ tsuga logs error-pattern-increases --from -24h --team my-team --env prod
 tsuga traces search --from -30m --query 'span_name:GET'
 ```
 
+### Summarize a trace
+
+Aggregates groups of similar spans into synthetic summary spans (marked with
+`spanAttributes.aggregation.is_summary`) for a compact view of large traces:
+
+```bash
+tsuga traces summarize --trace-id 78c99c5bb1e4a30297fa134b9dbec64f --from -30m
+```
+
+### Trace latency summary
+
+Summarizes where wall-clock time is spent in a trace: each slice of the timeline
+is attributed to the services with active leaf spans, with per-service totals:
+
+```bash
+tsuga traces latency-summary --trace-id 78c99c5bb1e4a30297fa134b9dbec64f --from -30m
+
+# Per-service totals only, without the range timeline
+tsuga traces latency-summary --trace-id 78c99c5bb1e4a30297fa134b9dbec64f --from -30m --no-ranges
+
+# Collapse timeline ranges shorter than 50ms (0 disables collapsing)
+tsuga traces latency-summary --trace-id 78c99c5bb1e4a30297fa134b9dbec64f --from -30m --min-range-duration-ms 50
+```
+
 ### Metrics
 
 ```bash
@@ -360,7 +384,7 @@ tsuga experimental promql -f query.json
 Or inline:
 
 ```bash
-tsuga experimental promql -d '{"query":"sum(rate(http_requests_total[5m]))","timeRange":{"from":1704067200,"to":1704070800},"step":"30s"}'
+tsuga experimental promql -d '{"query":"sum by (\"context.service.name\") (sum_over_time({\"traces.span.metrics.calls\", \"span.kind\"=\"SPAN_KIND_SERVER\"}[5m]))","timeRange":{"from":1704067200,"to":1704070800},"step":"30s"}'
 ```
 
 `timeRange.from` / `timeRange.to` are Unix timestamps in seconds.