@Sarah Terry Just to second what Joe said above "Is it possible to have a mix of the public and internal checkpoints assigned to the same Website check in the future?" - this would be a big step forward for us too unless LM are going to open new Checkpoint locations in the near future (in the UK / Europe region).

thanks

@Dave Smale you can actually use LM Collectors as checkpoint locations now - you just need to create an Internal Web Check to do so (instead of a regular, external Web Check).

Hi Sarah,  thanks for the swift response, apologies but let me explain our need more clearly...

We need to perform website checks from the internet from multiple locations.  While LM has 6 internet locations only 1 is close to the UK and the more remote sites appear unreliable.  We can only set a single timeout/download time to cover all monitoring locations but even at 30,000ms we still find that we are getting drops and false alarms.

Having a number of reliable checkpoint locations is crucial for us so we can protect against false positives and can obtain a reliable reading of how responsive a site actually is.

So we were wondering if LM intend to open any further checkpoint locations in the near future - hopefully in the UK or Europe ideally?

The [only] alternative we have currently is to build out our own "Collector virtual machines" in data centres around the UK and Europe and use the "Internal Web Check" functionality as you say.

Agree, we need a couple more Website check locations in the LM cloud side - The USA has 3 checkpoints, Asia, Australia & Europe have 1 a piece

how about a further website checkpoint from the London DC & another from a Central Europe location?

@Joe Tran The LA checkpoint is particularly burdensome for us to maintain. We do plan to retire it, but expect to be able to add new checkpoint locations in the upcoming year as well. We'll definitely look at requests such as the ones in this thread to determine where those new checkpoints should be added.

Re the LA checkpoint retirement notice, are you anticipating the SF checkpoint to be insufficient for California / West Coast US based website monitoring coverage?

Adding LAC-based checkpoints to the chorus as well as UK and Europe based checks. 

Quote

Los Angeles Web Check Location - Retirement Notice

Please be advised that we are retiring our Los Angeles web check location with v114 (targeted to release in early January). Our San Francisco location will still be available as a monitoring checkpoint within California. All Los Angeles web checks will automatically be migrated to San Francisco checks, unless the San Francisco location is already in use. Please contact your Customer Success Manager with any concerns.

Thanks and happy monitoring!

@Sarah Terry Fortunately, SF checkpoint is fine for our use cases but we do have to reconsider how our Website checks are configured. For some of our apps we will alert if >= 50% of checkpoints are in error and for our US-based client base, we only use the US-based checkpoints. We will have to revisit checkpoint assignments and alert triggers for our Website checks now.

We do have hardware and therefore Collectors across the country. Is it possible to have a mix of the public and internal checkpoints assigned to the same Website check in the future? Obviously, certain features won't be available (i.e. scripted Request and Response), but having that flexibility would be awesome. 

@Joe Tran we can definitely take that into consideration, thanks for the feedback!

Would be really keen to know if there has been any developments within LM in terms of bring a UK and EU monitoring station online in the future?

Failing that how about being able to have a mix of the public and internal checkpoints assigned to the same Website check in the future - or some mechanism so we can collate and graph their respective results on the same widget?

thanks