You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is also possible to supply a key on the command line (`--key KEY`).
179
+
180
+
### Probe Selection
181
+
182
+
The following probe selection options are available:
183
+
*`--probearea` select from areas. A comma separated list of `amount@area` where `area` can be `ww`, `west`, `nc`, `sc`, `ne`, `se`
184
+
*`--probeasn` select from ASNs. A comma separated list of `amount@ASN`
185
+
*`--probecc` select from countries. A comma separated list of `amount@CC` where CC is a valid country code
186
+
*`--probelist` provides an explicit list of probe IDs to include as a comma separated list.
187
+
*`--probeprefix` select from prefixes (IPv4 or IPv6). A comma separated list of `amount@prefix`
188
+
*`--probereuse` reuse probes from a precvious measurement. A comma separated list of `amount@msmID`
189
+
190
+
Multiple probe selection criteria can be sepcified; each of them add more probes to the selection.
191
+
192
+
`--probetaginc` and `--probetagexc` can be used to filter for probes that have been tagged (or not tagged) with those tags. Both are comma separated lists.
193
+
194
+
A default probe selection can be expressed in the configuration file (`/.config/goat.ini`) using entries with the above names in the `[probespec]` section, e.g.:
195
+
196
+
```
197
+
# default probe specifications for new measurements
198
+
[probespec]
199
+
probecc = ""
200
+
probearea = "9@ww"
201
+
probeasn = ""
202
+
probeprefix = ""
203
+
probelist = ""
204
+
probereuse = ""
205
+
```
206
+
207
+
### Timing
208
+
209
+
By default one-offs are scheduled, starting as soon as possible. You can specify a start time (`start`) in the future and for ongoings perhaps even a stop time (`stop`). Times can be specifies as:
210
+
* UNIX timestamps
211
+
* ISO8601 variants:
212
+
*`YYYY-mm-ddTHH:MM:SS` - leaving time details from the right makes them default to 0 (e.g. `2023-10-24` is valid and becomes `2023-10-24T00:00:00`)
213
+
214
+
### Measurement Types and Options
215
+
216
+
You can define one measurement per invocation. This can be one of: `ping`, `trace`, `dns`, `tls`, `ntp` or `http` (the last one with restrictions by the system). Each measurement needs a `target`, except DNS that needs a `name` to look up and uses `target` as the server/resolver to use if it's specified, otherwise uses the local resolver.
217
+
218
+
Common options for measurements include `interval`, `spread`, `tags` and some more.
219
+
220
+
Each mesurement type accepts a number of options, such as `abuf`, `qbuf`, `nsid`, `rd` for DNS, `minhop` and `maxhop` for trace, etc. Check the help page for the complete list of these.
221
+
222
+
### Output
223
+
224
+
For now the measurement scheduling request returns either the ID of the new measurement or an error if something went wrong.
225
+
226
+
227
+
## Status Checks
228
+
229
+
Provide a short summary of the results for a [measurement status check](https://atlas.ripe.net/docs/apis/rest-api-manual/measurements/status-checks.html). It needs a measurement ID, and by default it summarises the results (is there an alert, how many probes are in that state out of how many total, and with the `most` output formatter the list of alerting probes).
230
+
231
+
```sh
232
+
$ ./goatcli status -id 61953517 -output most
233
+
true 1 9 [1005382]
234
+
```
235
+
236
+
149
237
# Future Additions / TODO
150
238
151
-
*schedule a new measurement, stop existing measurements
239
+
* stop existing measurements
152
240
* modify participants of an existing measurement (add/remove probes)
0 commit comments