3 ms·
> Now imagine getting a page telling you that the tempurature [sic] in a rack where your job is running is hot. What are you supposed to do? Go and take a look
by chrisseaton 7y ago
> Now imagine getting a page telling you that the tempurature [sic] in a rack where your job is running is hot. What are you supposed to do?
Go and take a look at the rack? You'd have found and fixed the problem immediately in this case.
- growse 7y agoWhy would you waste time doing that when you don't even know there's a problem?
- chrisseaton 7y agoWhy does anyone heed a warning? In order to catch an issue before they get an error.
- growse 7y agoBut the point is that warnings are often not good predictors of problems. There's a good argument that "warning" on anything at all is an anti-pattern, because you're just attracting valuable attention towards something that may or may not be anything to worry about. Where warnings are useful are when "something is actually now going wrong" - they provide a valuable context that can help an engineer figure out what the issue might be, which is exactly how it worked in this case.
- deleted 7y ago[deleted]
- thethethethe 7y agoYou are missing the point. The scenario I presented was from the SREs perspective, not the workers in the datacenter
- chrisseaton 7y agoThe SRE can ask the data centre worker to take a look - or better yet the data centre worker would be notified directly and the SRE wouldn’t need to be in the loop.
- thethethethe 7y ago> The SRE can ask the data centre worker to take a look This is exactly what the blog post described
- deleted 7y ago[deleted]