Go to All Forums

Round Robin Location Checks

It would be nice if you could have website checks occur in a round robin fashion based on locations that you choose. Today it always checks from the primary unless there is an issue. There may however be an issue from a specific location that is never seen because things are working fine for the primary location. 
Like (4) Reply
Replies (7)

Re: Round Robin Location Checks

+1
This bit us recently as well, missed catching an internet routing issue for 30mins because our primary location was unaffected.
Like (0) Reply

Re: Re: Round Robin Location Checks

Hello,

Our primary reason for this polling strategy is to have consistent reporting in the dashboards. We show graphs based on primary locations statistics in our dashboards. When we do round-robin monitoring,tt might have more fluctuating graph rather than smooth one. Do you think that is fine ?

Following are the other options:

  • Do uptime monitoring alone from secondary locations more frequently
  • Do one another secondary location check along with primary location
  • Allow to define additional primary locations for a monitor and do polling on configured intervals
  • As you suggested provide current option along with option to choose round robin polling option

What would you prefer in the above.

We shall think on the probable enhancement here.

Raghavan

Like (0) Reply

Re: Round Robin Location Checks

I think user "options" are always the best :) 
  • Do uptime monitoring alone from secondary locations more frequently
I like this but I'd add to make this configurable. Meaning you would have the choice of primary interval and then secondary round robin interval. 
  • Do one another secondary location check along with primary location
If the first option was implemented this wouldn't be needed. 
  • Allow to define additional primary locations for a monitor and do polling on configured intervals
Think this is a good option as well. 
  • As you suggested provide current option along with option to choose round robin polling option

If only one were to be implemented I would vote for having a primary check with its own interval and then round robin check of all secondaries with their own interval. IE Primary = California every 1 minute and Secondary = Tokyo, Australia, London etc ever 3 minutes meaning each (in a 3 secondary scenario) would get hit every 9 minutes.
Like (0) Reply

Re: Round Robin Location Checks

Just a comment on an undocmumented "feature" that I found out about today.  All secondary checks currently happen every 30 minutes. 

Like (0) Reply

Re: Re: Round Robin Location Checks

Hello Damian,

You're right. In general, the primary location checks are based on the frequency set by the user, and the secondary locations poll every 30 minutes (we call it Hourly Poll - Polling from all secondary Locations twice an hour), by default. We'd encourage you to read our Kbase article to learn more about Site24x7's intelligent polling logic.

However, you can always get a higher and/or same poll frequency (as your primary location) for your secondary test location too; just switch to our special Enterprise Custom Plan by contacting Site24x7 Support

Regards,

Abhiram

Like (0) Reply

Re: Re: Re: Round Robin Location Checks

Thanks for the info @Abhiram. As of yesterday when I was speaking wtih Support they were not aware of this being documented anywhere, hence my comment. Was this KB just updated to reflect this or did Support just not have the information available? 


Also - This forum post is all in regards to the ability to do round robin or other frequency/methods of checks with the secondary monitors. It sounds like this feature partially already exists but only for an additional fee or custom plan? 

Like (0) Reply

Re: Re: Re: Re: Round Robin Location Checks

Hello Damian,

Sorry for any wrong inference that could have been concluded from my above statement. Site24x7 entirely applies a predictable polling from a location logic to ensure a uniform and intelligible reporting. We do not offer a Round Robin based monitoring since it gives too many spikes between polls because of latency differences due to different geographical conditions.

Regards,

Abhiram

 

 

Like (0) Reply

Was this post helpful?