[jborichevskiy]

I wonder if they track Github Status traffic volume as some sort of meta-indicator? Is it even viable?

I was futzing around with the description for a PR and hitting save wouldn't update it, yet clicking edit would show the text I expected to see.

Suspecting something was up I checked Github Status but it was green across the board. Assuming enough other people hit the same chain of events, could it provide a reliable enough indicator of an issue?

[spondyl]

> I wonder if they track Github Status traffic volume as some sort of meta-indicator? Is it even viable?

Sure, the previous decent sized company (~1000+ devs) had that exact metric available.

Visits to the status page generally that is. Now whether you could actually correlate that to an increase in errors for a particular component, no so much ;)

I'm sure it's totally feasible but it requires a certain amount of discipline to have consistency in logging/metric standards across all your applications to some extent.

Even worse, some applications would return a shared error page but internally, I believe it was logged as a 301 redirect until someone spotted it :)

[jborichevskiy]

Hah, that's awesome.

> Now whether you could actually correlate that to an increase in errors for a particular component, no so much ;)

Yep, makes sense. I was picturing a broad "Something Bad Happened, Go Investigate" notification. But I imagine the sensitivity would have to be tuned, especially to account for massive traffic increases from places like HN.

> Even worse, some applications would return a shared error page but internally, I believe it was logged as a 301 redirect until someone spotted it :)

Yikes!