Open corneliusroemer opened 9 months ago
IMO: A full stacktrace is better than no stacktrace - and this is the default behavior when logging exceptions. I.e. logging the full stacktrace is easy, logging no stacktrace is easy. Anything in between is not worth the implementation effort.
Also one learns to read Java error messages over time ;)
You're most likely right! However, the issue might be that asking to create a group that already exists shouldn't trigger a warning/exception. What do you think?
That's of course debatable ;) We could change that to info. The log message comes from our general exception handler that logs all exceptions. Maybe it's enough to log 4XX errors at info.
I've had a look at backend logs and noticed that there's a massive traceback when a user tries to create a group that already exists - it's strange this creates such a large exception log: