4 ms·

> Error budgets and the SRE model are haute couture. The error budget does not mean that you don't read the errors. It is just a way to adjust the amount of ti

> Error budgets and the SRE model are haute couture. The error budget does not mean that you don't read the errors. It is just a way to adjust the amount of time you spend fixing bugs versus pushing new features. Also, as mentioned... > Over the next six months, the team iterates, listens to customers, and delivers a ton of value. As a result, traffic levels grow to a rate of 10,000,000 requests per year. The people who advocate looking at errors in aggregate may have much, much busier services.

doctor_eval 3y ago
I was about to write that some kinds of advice are very good in some scenarios and very bad in others. The arguments always seem to skirt that middle ground where good advice goes bad (or vice versa) 10MM requests per year is 20 requests/minute. Most people will probably be working on services at this scale, or less. So the advice is good, but not global, and the qualification is important.
jacurtis 3y ago
I was confused when I saw them mocking error budgets at the end. It shows that they don't understand what error budgets are. What they describe themselves doing is basically an error budget by a different name. We have an error budget at work and we still read essentially every error. There is a long tail of errors that might show up once or twice a week or month and I'll admit that I might have missed those, but within any practical sense, my team is still aware of any error that is contributing against our error budget. We resolve errors too, even while under budgetm because if we didn't then we would go over our error budget since new errors pop up all the time, so you need to resolve existing errors because new ones are introduced constantly. Pulumi seems to think that companies with Error Budgets just wait until they are out of compliance to fix errors and then must only resolve enough to get back under budget.

doctor_eval 3y ago

I was about to write that some kinds of advice are very good in some scenarios and very bad in others. The arguments always seem to skirt that middle ground where good advice goes bad (or vice versa) 10MM requests per year is 20 requests/minute. Most people will probably be working on services at this scale, or less. So the advice is good, but not global, and the qualification is important.

jacurtis 3y ago

I was confused when I saw them mocking error budgets at the end. It shows that they don't understand what error budgets are. What they describe themselves doing is basically an error budget by a different name. We have an error budget at work and we still read essentially every error. There is a long tail of errors that might show up once or twice a week or month and I'll admit that I might have missed those, but within any practical sense, my team is still aware of any error that is contributing against our error budget. We resolve errors too, even while under budgetm because if we didn't then we would go over our error budget since new errors pop up all the time, so you need to resolve existing errors because new ones are introduced constantly. Pulumi seems to think that companies with Error Budgets just wait until they are out of compliance to fix errors and then must only resolve enough to get back under budget.