# A Full Example
This following request payload is an example of the features we've discussed:
{
"definitions": [
{
"target": "www.ripe.net",
"description": "My Complex Measurement",
"type": "traceroute",
"af": 6,
"resolve_on_probe": true,
"is_public": true,
"packets": 16,
"protocol": "ICMP",
"paris": 99,
"firsthop": 30,
"interval": 1800,
"is_oneoff": false
},
{
"target": "www.ripe.net",
"description": "My Complex Measurement",
"type": "ping",
"af": 4,
"resolve_on_probe": false,
"is_public": false,
}
],
"probes": [
{
"requested": 10,
"type": "area",
"value": "WW"
},
{
"requested": 5,
"type": "country",
"value": "GR"
},
{
"requested": 5,
"type": "country",
"value": "CA"
},
{
"requested": 3,
"type": "probes",
"value": [55,19,252]
},
{
"requested": 1,
"type": "udm",
"value": 1000002
}
],
"start_time": 1461807395,
"stop_time": "2018-01-01T12:00:00Z",
"is_oneoff": true
}
Note that this example has multiple measurement definitions, multiple probe participation requests and some defaults set outside the definitions
section. So, the global start_time
and stop_time
propagate into definitions because they have it missing. The global is_oneoff
propagates only to the second measurement because the first one has it already initialized. As a result we have two measurements with conflicting is_oneoff
and it will fail until we remove global is_oneoff
or explicitly set is_oneoff
to the same value for both measurements.