https://giedrius.blog/categories/filebeat/Recent content in Filebeat on Giedrius StatkevičiusHugoen-USWed, 08 Jul 2020 20:28:27 +0000https://giedrius.blog/2020/07/08/crash-only-software-in-practice-with-filebeat-on-kubernetes/Wed, 08 Jul 2020 20:28:27 +0000https://giedrius.blog/?p=676<p>Some time ago I read an article called <a href="https://lwn.net/Articles/191059/">Crash-only software: More than meets the eye</a>. It&rsquo;s about an idea that sometimes it is easier and faster to just crash and restart the whole process than handle the error appropriately. Sometimes, obviously, it is even impossible to handle errors as in, for example, <a href="https://en.wikipedia.org/wiki/Kernel_panic">Linux kernel panics</a>. Nowadays programming languages especially tend to make it so that it would be very hard, almost impossible to <em>not</em> handle errors. For instance, Rust has a <a href="https://doc.rust-lang.org/std/result/enum.Result.html">type</a> that either represents success or an error. You have to explicitly unwrap that type and decide what to do in either case. But, apart from those obvious cases, I haven&rsquo;t seen any examples of crash-only software. Until recently.</p>