more than 10 concurrent measurements to the same target
Hi! When scheduling checks I often get the error: "We do not allow more than 10 concurrent measurements to the same target." Imo this is not correct. Yes, I do schedule more then 10 measurements to the same target, but they are not concurrent. They are sequential - one ofter the other. Thus, it would be great if this check could be fixed to consider start and stop times. Thanks Klaus
On Dec 9, 2015, at 1:38 PM, Klaus Darilion <klaus.mailinglists@pernau.at> wrote:
Hi!
When scheduling checks I often get the error: "We do not allow more than 10 concurrent measurements to the same target."
Imo this is not correct. Yes, I do schedule more then 10 measurements to the same target, but they are not concurrent. They are sequential - one ofter the other. Thus, it would be great if this check could be fixed to consider start and stop times.
I have found a workaround for this by using DNS names in addition to the IP address. Bonus points if you create your own unique DNS name for the time period in question. - Jared
On Wed, Dec 09, 2015 at 07:38:52PM +0100, Klaus Darilion <klaus.mailinglists@pernau.at> wrote a message of 12 lines which said:
When scheduling checks I often get the error: "We do not allow more than 10 concurrent measurements to the same target."
Imo this is not correct.
I believe that the counter is global (not just your measurements). I often see this error when measuring 8.8.8.8 (a very popular target).
On 11.12.2015 16:11, Stephane Bortzmeyer wrote:
On Wed, Dec 09, 2015 at 07:38:52PM +0100, Klaus Darilion <klaus.mailinglists@pernau.at> wrote a message of 12 lines which said:
When scheduling checks I often get the error: "We do not allow more than 10 concurrent measurements to the same target."
Imo this is not correct.
I believe that the counter is global (not just your measurements). I often see this error when measuring 8.8.8.8 (a very popular target).
That's what I heard too. But I have the problem when targeting my server which for sure nobody test except me. I also have the problem even when all my measurements to this target are already stopped. It seems that this counter is not updated in real time. regards Klaus
Hi, On 12/11/15 5:39 PM, Klaus Darilion wrote:
On 11.12.2015 16:11, Stephane Bortzmeyer wrote:
I believe that the counter is global (not just your measurements). I often see this error when measuring 8.8.8.8 (a very popular target).
That's absolutely right.
That's what I heard too. But I have the problem when targeting my server which for sure nobody test except me. I also have the problem even when all my measurements to this target are already stopped. It seems that this counter is not updated in real time.
regards Klaus
It can happen when you use one-offs. RIPE Atlas infrastructure uses a timeout of ~15 minutes after starting one-off measurement before marking it as finished. You also can check what measurements are/were performed against a particular target on the RIPE Stat on "Activity" tab. Scroll down to the very last "RIPE Atlas measurement target" view. Cheers, /vty
participants (4)
-
Jared Mauch -
Klaus Darilion -
Stephane Bortzmeyer -
Viktor Naumov