On 2022-12-16 at 12:56, Robert Kisteleki wrote:
Hi,
The definition of a "small" test could be something like;
- maximum 20 probes
- runs for maximum 60 minutes
- is repeated maximum 10 times
(if you run every 300sec you have to limit the endtime to 50 minutes)
What would you propose the API to do if this rule is violated? Should it
outright refuse the measurement, or should it silently turn on the
public flag (silently, because even if we emit a warning, it is probably
never seen by a human...)?
I think the safest thing would be to refuse with an error message. Just
override a setting with just a warning is probably not enough, as you wrote.
With such limits you can troubleshoot things (non-publicly) but you
can't build your monitoring system on top of that.
I guess this hinges on what level of support (legal, technical or other)
we're aiming for when it comes to others building services on top of
RIPE Atlas.
I really love RIPE Atlas and all the possibilities that come with an
open and mature platform. I think as much as possible should be open and
reusable by others. However, I understand that some people in some cases
have other wishes.
Regards,
// mem
--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas
