@tsuga/cli 1.0.12 → 1.0.13
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +25 -11
- package/dist/cli.js +51 -52
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -37,7 +37,7 @@ Priority order: `--operation-api-key` flag → `TSUGA_OPERATION_API_KEY` env var
|
|
|
37
37
|
|
|
38
38
|
## Configuration
|
|
39
39
|
|
|
40
|
-
Show current configuration:
|
|
40
|
+
Show current configuration (includes defaults):
|
|
41
41
|
|
|
42
42
|
```bash
|
|
43
43
|
tsuga config
|
|
@@ -57,26 +57,22 @@ Commands have built-in defaults so you can omit common flags:
|
|
|
57
57
|
Override defaults persistently:
|
|
58
58
|
|
|
59
59
|
```bash
|
|
60
|
-
tsuga
|
|
61
|
-
tsuga
|
|
60
|
+
tsuga config set default from -1h
|
|
61
|
+
tsuga config set default query 'level:ERROR'
|
|
62
62
|
```
|
|
63
63
|
|
|
64
|
-
|
|
65
|
-
|
|
66
|
-
```bash
|
|
67
|
-
tsuga defaults
|
|
68
|
-
```
|
|
64
|
+
Current defaults are listed by `tsuga config` (custom overrides marked with `*`).
|
|
69
65
|
|
|
70
66
|
Reset all custom defaults:
|
|
71
67
|
|
|
72
68
|
```bash
|
|
73
|
-
tsuga
|
|
69
|
+
tsuga config reset defaults
|
|
74
70
|
```
|
|
75
71
|
|
|
76
72
|
Clear a single default by setting it to an empty value:
|
|
77
73
|
|
|
78
74
|
```bash
|
|
79
|
-
tsuga
|
|
75
|
+
tsuga config set default cluster ''
|
|
80
76
|
```
|
|
81
77
|
|
|
82
78
|
## Clusters
|
|
@@ -90,7 +86,7 @@ tsuga cluster list
|
|
|
90
86
|
Pick the cluster you want to use by default via the defaults mechanism:
|
|
91
87
|
|
|
92
88
|
```bash
|
|
93
|
-
tsuga
|
|
89
|
+
tsuga config set default cluster <cluster-id>
|
|
94
90
|
```
|
|
95
91
|
|
|
96
92
|
Override per-command without persisting:
|
|
@@ -130,6 +126,16 @@ You can also pass JSON inline with `-d`:
|
|
|
130
126
|
tsuga teams create -d '{"name": "Platform", "visibility": "public"}'
|
|
131
127
|
```
|
|
132
128
|
|
|
129
|
+
### Explaining a call with `--rationale`
|
|
130
|
+
|
|
131
|
+
API-calling commands accept an optional `--rationale` flag to record why they are being run.
|
|
132
|
+
It does not change the result; the text is sent as a request header and recorded in the
|
|
133
|
+
backend request log, which is useful for understanding agent behavior.
|
|
134
|
+
|
|
135
|
+
```bash
|
|
136
|
+
tsuga logs patterns --rationale "exploring telemetry to investigate prod outage"
|
|
137
|
+
```
|
|
138
|
+
|
|
133
139
|
### Available resources
|
|
134
140
|
|
|
135
141
|
`cloud-resources`, `dashboards`, `ingestion-api-keys`, `monitors`, `notification-rules`, `notification-silences`, `quality-reports`, `retention-policies`, `routes`, `services`, `tag-policies`, `teams`
|
|
@@ -321,6 +327,14 @@ tsuga docs search 'log routes'
|
|
|
321
327
|
tsuga docs get getting-started/send-your-first-logs
|
|
322
328
|
```
|
|
323
329
|
|
|
330
|
+
## Feedback
|
|
331
|
+
|
|
332
|
+
Report friction with Tsuga tools or APIs (a failing command, unusable output, confusing behavior):
|
|
333
|
+
|
|
334
|
+
```bash
|
|
335
|
+
tsuga feedback the traces command keeps timing out on large services
|
|
336
|
+
```
|
|
337
|
+
|
|
324
338
|
## Tips
|
|
325
339
|
|
|
326
340
|
Default output is JSON, so you can pipe to `jq`:
|