Limiting check locations - Feature about cf-workers-status-page

[eidam]

Thank you for the discussion! I am currently working on launching something new that you might like and might solve more configurability.. Would you be interested in beta access? Gonna share it on my twitter once ready
https://twitter.com/adam_janis/status/1354550480068878339

[eidam]

Hey @mistermantas, it checks on every CRON trigger. You need to set it to 2 minute CRON (or higher) in case you want fit to the free tier :) https://github.com/eidam/cf-workers-status-page#workers-kv-free-tier

[eidam]

There is no way to control the locations at the moment as the CRON triggers locations are not picked randomly on each run. Instead, they are scheduled to the least used datacenters during the day. For example, they are being checked from Australia for 6 hours a day. It would be possible to ignore specific locations, but it would also mean you would have 6 hours gaps of no data at all.

The defined locations are just for mapping the IATA code to a friendlier name.

Would you be interested in the "ignoring" locations feature even if that would mean x hours gaps in monitoring?

[oliverlucas85]

Reading the documentation it did kind of suggest that it would be run from the least used datacentres, I'm not sure that having a gap would be good. I think the only thing that may be good is trying to identify why requests get blocked from Australia, e.g. took too long or something.. If that information was available I think that would be a feature.

Sad times, I'll have to go hunt around for another solution. The UX and easy configurability really appealed.

Feel free to close this off!

Thanks

[eidam]

@oliverlucas85 are Europe locations ok with you? I do have a beta version of what I promised :)
The UI is a bit clumsy and the status page is per account (there will be an option to create as many status pages as you want), but you can get 1-minute managed checks with no need to deploy anything. You will be able to deploy your own workers or whole Statusflare to your infra in the future.

Feel free to try it out at https://dash.statusflare.com

[oliverlucas85]

Oooo interesting! Europe locations would be perfect for our requirements - How are you controlling the check locations? Will there be this blackout as you said before, or are you utilizing Cloudflare workers in a different way now (read, constantly running on all worker edge locations?)

I've given it a login and setup a test check and they do appear to be connecting from Europe so that's a win!

[eidam]

Thanks for the feedback! It works a bit differently and the "managed" checks are actually scheduled from my servers, so it does not rely on the CRON triggers scheduled in one datacenter at a time directly. So the checks are now scheduled kinda randomly from my server locations.

I am about to add one US location for a couple of days, however, I do plan to add a feature to exclude any of the locations before I will start adding new locations permanently.

[eidam]

You will be able to change the Status Page appearance as well, hopefully going to release Statusflare beta by end of February.

[mistermantas]

I believe this is a question for this open source version of the status page as opposed to the hosted version which I didn't know existed -- I deployed it to a free instance of cF Workers just to try it out and it ran into the 1000 max KV operations/day. How many times does the status page actually check the URL?

[mistermantas]

Hey @mistermantas, it checks on every CRON trigger. You need to set it to 2 minute CRON (or higher) in case you want fit to the free tier :) https://github.com/eidam/cf-workers-status-page#workers-kv-free-tier

Thanks & much love, I want to recommend this to people for monitoring services. :)

[dzvision]

If we could select which location it would be great. (Or having all of them, fastest first)