-
Notifications
You must be signed in to change notification settings - Fork 18k
web: monitoring for *.golang.org properties #22603
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
cc @broady who has done the alerts for playground (and other sites?) |
We should move everything to services instead of versions of the godoc app. EDIT: we should still move everything to services but we can still set up monitoring on those properties using the legacy GAE |
Change https://golang.org/cl/96416 mentions this issue: |
Also bump Go from 1.8 to 1.10, and change how the static binary is built to avoid warnings during link. Updates golang/go#21315 Updates golang/go#22603 Change-Id: I426491d48f787a77cb3eea4dff4d11f474236548 Reviewed-on: https://go-review.googlesource.com/96416 Reviewed-by: Andrew Bonventre <[email protected]>
Change https://golang.org/cl/97516 mentions this issue: |
This reverts the status changes to devapp from CL 96416 This will go into its own server instead. Updates golang/go#21315 Updates golang/go#22603 Change-Id: Icb17a5915124241b2ef97a1ee2e9a0e4298784ce Reviewed-on: https://go-review.googlesource.com/97516 Reviewed-by: Andrew Bonventre <[email protected]>
Uptime monitoring has been added for
|
Change https://golang.org/cl/210740 mentions this issue: |
The plan was to have a stand-alone status server that just kept track of the last-reported status updates from various things, and then have components self-report their status, and then the status server would report a lack of timely updates as a failure. But this was never completed and a bunch of health checking went into the coordinator instead, which kinda works well enough. I still think this project should be revived, but maybe it could use some existing cloudy product instead. In any case, I don't see myself finishing this, so I'm going to delete this unused code for now. Others can resurrect it if desired if/when they move stuff out of the coordinator. Updates golang/go#21315 Updates golang/go#22603 Change-Id: I2d3c33358855206ea98283c9871c6e050e931a43 Reviewed-on: https://go-review.googlesource.com/c/build/+/210740 Reviewed-by: Alexander Rakoczy <[email protected]> Run-TryBot: Alexander Rakoczy <[email protected]> TryBot-Result: Gobot Gobot <[email protected]>
talks.golang.org was down for several hours, but there were no alerts.
We should do an inventory of our web properties and set up (at least) basic reachability checks, along with a plan for how we’d like to handle the alerts.
related issues:
#21315
#15760
/cc @bradfitz @adams-sarah
The text was updated successfully, but these errors were encountered: