4 ms·
The best part about trying to measure exceptions or work towards zero exceptions is the system you put in place to detect them. What you care about eliminating
by thinkingkong 11y ago
The best part about trying to measure exceptions or work towards zero exceptions is the system you put in place to detect them.
What you care about eliminating are the ones that happen a lot, or the ones that happen immediately following a release or feature flag being turned on.
If you aren't measuring or capturing things in a reasonable way, that's where you'll feel tons of pain. Otherwise I agree with a few of the comments; getting to zero is a noble goal but perhaps not the point.
- otakucode 11y agoI've always been surprised that there aren't widely-used tools (I think they do exist but just aren't very popular) that monitor logs and analyze them for irregularities. Have it learn what messages are 'normal' and only send up an alarm when something statistically significant crops up. It doesn't even have to be heavy machine-learning, just some basic statistical analysis would probably help a great deal. Add in correlating multiple logs with one another (increasingly an issue when you've got dozens of servers actually running your application, any of which could be raising important messages while all of them clutter the log with usually-unimportant messages). Taking a firehose of data and breaking it down into what needs attention is something software should be much better at than human beings.