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

StatusPage.io degraded performance reporting #6

Open
bergie opened this issue Sep 23, 2015 · 1 comment
Open

StatusPage.io degraded performance reporting #6

bergie opened this issue Sep 23, 2015 · 1 comment
Milestone

Comments

@bergie
Copy link
Member

bergie commented Sep 23, 2015

In situations like the recent AWS outage the Heroku API may be down, affecting guv's ability to auto-scale our infrastructure.

2015-09-23T16:24:29.463496+00:00 app[guv.1]: ERROR: { [Error: Expected response to be successful, got 503]
2015-09-23T16:24:29.463501+00:00 app[guv.1]:   statusCode: 503,
2015-09-23T16:24:29.463503+00:00 app[guv.1]:   body: 
2015-09-23T16:24:29.463504+00:00 app[guv.1]:    { id: 'unavailable',
2015-09-23T16:24:29.463506+00:00 app[guv.1]:      message: ' Heroku has temporarily disabled this feature, please try again shortly. See https://status.heroku.com for current Heroku platform status. ' } }

Would be nice to report this as "degraded performance" to statuspage.io via their API:

http://doers.statuspage.io/api/v1/components/

Related to #5

@bergie
Copy link
Member Author

bergie commented Sep 23, 2015

Similarly, if guv can't talk to the message queue, we should report that as an outage

@jonnor jonnor added this to the 0.2 milestone Mar 14, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants