3 ms·
Normally, this solution works great. At Twitter's scale with the number of API users they had, I can't imagine how they'd filter the signal out of the noise.
by shadowgovt 4y ago
Normally, this solution works great.
At Twitter's scale with the number of API users they had, I can't imagine how they'd filter the signal out of the noise.
This is very much a "someone would have had to know we're using our own API to avoid this disaster" scenario, which is an institutional knowledge problem. The kind of problem that gets hard to solve when XX% of your workforce suddenly left to seek new opportunities.
- jeffbee 4y agoSorry no. It is not an oral history problem. You simply group the stats by caller. “At Twitter scale” implies they already have this dashboard.
- shadowgovt 4y agoAh, good point. Twitter should have been the largest caller. That 467 error code suggests to me something else is going on and Twitter is emitting the wrong error message (467 isn't a standard HTTP, so I'm wondering if something lower-level emitted a 467 error, it was misinterpreted as an HTTP status, and the error string chooser logic is giving that API access error message due to fall-through).