Skip to content
This repository has been archived by the owner on Dec 2, 2020. It is now read-only.

Improve monitoring of pulls website #43

Open
mattl opened this issue Nov 21, 2017 · 4 comments
Open

Improve monitoring of pulls website #43

mattl opened this issue Nov 21, 2017 · 4 comments

Comments

@mattl
Copy link
Contributor

mattl commented Nov 21, 2017

Restart things when they're down, etc.

@foolip
Copy link
Member

foolip commented Nov 22, 2017

@mdittmer already has some monitoring at https://bit.ly/ecosystem-infra-status, but we removed ecosystem-infra from notifications because of noise.

@mattl
Copy link
Contributor Author

mattl commented Nov 22, 2017

Oh yeah, and I have my own monitoring too, but it just tells me when its down. I'd like to improve that to actually do something.

@foolip
Copy link
Member

foolip commented Nov 22, 2017

Oh, so responding with 504 counts as being up? I have something very rudimentary in https://github.com/whatwg/misc-server/blob/master/test/wiki.js, but I guess you'd want something that runs more than every 24 hours :)

@mattl
Copy link
Contributor Author

mattl commented Nov 22, 2017

No, it doesn't count as being up. Ideally, when that happens something can restart the service after a few retries. This helps in the situation where things are down at 3am more than when things are down at 3pm on a weekday.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants