Re:Show HN: WebGazer – Simple and Affordable Website Monitor...
by stevekemp on Thursday October 25, 2018 @12:35PM
(#18302217)
For the future it should be "peace of mind", rather than "piece of mind". English is confusing like that!
Re:Show HN: WebGazer – Simple and Affordable Website Monitor...
by nodesocket on Thursday October 25, 2018 @12:08PM
(#18301983)
Is there a way to configure a check to have to fail across 2 or even 3 locations before being considered down?
Also, didn't see a list of data center locations and providers. Are you multi-provider (AWS, Google Cloud, DigitalOcean).
Re:Show HN: WebGazer – Simple and Affordable Website Monitor...
by th0th on Thursday October 25, 2018 @01:33PM
(#18302695)
Before sending down notifications, we validate incidents 4 times from different servers (TBH, not from different locations). List of IP addresses that a WebGazer request might originate from will be available on our docs soon.
Re:Show HN: WebGazer – Simple and Affordable Website Monitor...
by alexandernst on Thursday October 25, 2018 @11:41AM
(#18301750)
The "Sign up" button (in "Growth" plan) doesn't work (in Safari). "SyntaxError: The string did not match the expected pattern."
Re:Show HN: WebGazer – Simple and Affordable Website Monitor...
by th0th on Thursday October 25, 2018 @12:29PM
(#18302173)
Hey, thanks for the heads up. It should be fixed now :)
WebGazer is a website monitoring service checking your website on a regular basis. It notifies you with instant alerts in case of a problem. That way, you have a piece of mind about the status of your service without manually checking it.
You can publish the performance overview of the gazers through WebGazer Status Pages. Status page is simply a gateway to users. Successful companies are now going transparent and removing the wall between users with public announcement pages
Publish performance of your system to users for more transparency.
Update for any ongoing difficulties on the infrastructure (we know everyone has their servers on fire now and then)
Close the gap between your DevOps and audience.