4 ms·
A good logging tool will group similar errors together so one error occurring 10,000 times shows once in the list. But what I’ve found is a whole lot of errors
by Gigachad 4y ago
A good logging tool will group similar errors together so one error occurring 10,000 times shows once in the list.
But what I’ve found is a whole lot of errors are things timing out which are kind of an issue, but not something you can really investigate or solve.
- arp242 4y agoGrouping helps, but often errors are distinct enough that they will get duplicated regardless, especially after updates which changes the stack trace. To be honest it's been a few years since I used these tools, but last time it was helpful but very much less-than-perfect. > a whole lot of errors are things timing out which are kind of an issue, but not something you can really investigate or solve. Depends what is timing out; if it's SQL queries then you should probably do something somewhere, if it's HTTP connections then you probably shouldn't log them as an error but as info/debug, keep some aggregate statistic somewhere, or just not do anything with it at all (depending on your scale and what you need).
- lanstin 4y agoOr switch to gRPC :) if it is internal to the data center traffic.
- AtNightWeCode 4y agoMost logging tools if used correctly separates static messages from dynamic values. Which makes grouping trivial.