Re: [go-nuts] Slog and error tracing

2023-08-10 Thread 'Jim Idle' via golang-nuts
You are logging the same error many times and then trying to solve that in the logs. Try this: Only log the error where it is handled, otherwise wrap it and return it without logging. At some point, you will log it as either an error if there is nothing you can do about it, or a warning if someho

[go-nuts] Slog and error tracing

2023-08-10 Thread jal...@gmail.com
Hi all, I've adopted slog and I am really loving the library. As I have used this on my team, I've noticed a repetitive problem with error wrapping and I am curious how other folks have handled this problem. Lets say you are calling a sequence of functions where one function depends on the r