<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>cramjabsyn</author><text>&amp;gt; The reasonable way to notice is to have alerts for any unexpected restarts. Relying on noticing intermittent service disruption is bound to fail.&lt;p&gt;I&amp;#x27;d argue that unexpected restarts should alert beyond a threshold.  Alerting on every occurrence is too noisy.  If an individual unit failure causes a service disruption architecture improvements are needed.</text><parent_chain><item><author>pikahumu</author><text>The reasonable way to notice is to have alerts for any unexpected restarts. Relying on noticing intermittent service disruption is bound to fail. And so is &amp;quot;remembering to check for this&amp;quot;:&lt;p&gt;&amp;gt; in the future I&amp;#x27;m going to want to remember to check for this&lt;p&gt;Whenever you think that sentence, you should notice this as a red flag and re-think your approach. You &lt;i&gt;will&lt;/i&gt; forget. And if not you, then somebody else in your team. You need automation for things you can forget, otherwise your mental checklists will grow too large to handle and are just a distraction.</text></item></parent_chain></comment><story><title>Systemd auto-restarts of units can hide problems from you</title><url>https://utcc.utoronto.ca/~cks/space/blog/linux/SystemdRestartHidesProblems</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>harry8</author><text>This is good advice imho.&lt;p&gt;Away from things that can be automated and are important you have a checklist and tick things off with a pen. Add $this to the list.&lt;p&gt;Atul Gawande is worth reading in general and on this topic. [1] He turned it into a book I haven&amp;#x27;t yet read.&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.newyorker.com&amp;#x2F;magazine&amp;#x2F;2007&amp;#x2F;12&amp;#x2F;10&amp;#x2F;the-checklist&quot; rel=&quot;nofollow noreferrer&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.newyorker.com&amp;#x2F;magazine&amp;#x2F;2007&amp;#x2F;12&amp;#x2F;10&amp;#x2F;the-checklist&lt;/a&gt;</text><parent_chain><item><author>pikahumu</author><text>The reasonable way to notice is to have alerts for any unexpected restarts. Relying on noticing intermittent service disruption is bound to fail. And so is &amp;quot;remembering to check for this&amp;quot;:&lt;p&gt;&amp;gt; in the future I&amp;#x27;m going to want to remember to check for this&lt;p&gt;Whenever you think that sentence, you should notice this as a red flag and re-think your approach. You &lt;i&gt;will&lt;/i&gt; forget. And if not you, then somebody else in your team. You need automation for things you can forget, otherwise your mental checklists will grow too large to handle and are just a distraction.</text></item></parent_chain></comment><story><title>Systemd auto-restarts of units can hide problems from you</title><url>https://utcc.utoronto.ca/~cks/space/blog/linux/SystemdRestartHidesProblems</url></story>