Allow reusing measurement IDs for selecting same group of probes

[jimaek]

Allow reusing measurement IDs for selecting same group of probes

[MartinKolarik]

In terms of the API, I'm thinking of overloading the locations array so that if you pass in a string, it's interpreted as a measurement ID, and the locations are reused from that ID.

Additionally, if locations.length === 1 and it's magic, and it doesn't match anything, as the last step, we should try to interpret it as a measurement ID as well. This will allow users to paste the ID into any of our tools that support the magic mode.

[alexey-yarmosh]

measurement with id1 had 20 probes, user starts a new measurement with locations: id1 but API found only 19 of prev probes (1 is disconnected right now). Should api proceed and return OK {probesCount: 19} or try replace missing or send 422?

[MartinKolarik]

OK and 19 but the client must know which probe that is (order of results must match) since the goal is comparing the two runs.

I'm thinking the best way might be keeping the probe in the results array and filling the result with a new probe-level error. Similar to probe timeout but with a different type probably - unavailable or offline ?

[alexey-yarmosh]

offline status makes sense. Then, since it is treated as a probe with error, probesCount should be 20 I think.

[MartinKolarik]

Yes.