Post Status Updates for Latency Issues

[ksheurs]

Establish an acceptable level of latency and post updates if this value is exceeded by x percentage.

[mjallday]

+1. we should definitely update when there is any degradation of the API

/cc @mahmoudimus @jkwade @steveklabnik

[steveklabnik]

Yup, 👍 here too—
Sent from Mailbox for iPhone

On Tue, Jan 28, 2014 at 10:02 AM, Marshall Jones [email protected]
wrote:

+1. we should definitely update when there is any degradation of the API

/cc @mahmoudimus @jkwade @steveklabnik

Reply to this email directly or view it on GitHub:
#18 (comment)

[remear]

What if we had something like https://status.github.com/messages.

[mjallday]

@dmdj03 - do you still have the mocks for the latency graphs that you created last year?

[dmdj03]

Yes, @kyungmin and I are thinking of placing them on a secondary page with a link from the main status page. The graph seems to interrupt the flow of the status information which is all about uptime. API response times are also only specific to the API section, so it feels out of place having it span the page across JS and Dashboard.