@tsuga/cli 1.2.0 → 1.3.0

package/README.md

@@ -316,6 +316,21 @@ Aggregates groups of similar spans into synthetic summary spans (marked with
 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
@@ -369,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.