-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing exception class name in 500 handling #301
Comments
Maybe I'm mistaken, and was the exception class name never printed to the logs, as in Play1 I cannot find it: Or maybe it was part of the stacktrace in the past. |
Would you mind showing a few log line with and without the requested change as an example?
Are you talking about PR #208? |
Here you go, straight from our logs (with some text replaced to not share too much internals):
Say I want to catch this exception, how do I find the actual class name of the exception? Sure, I'll find it, but it would we nice if it was in the logs.
No. We recently moved all code to Kotlin. Since I seem to remember that we used to be able to see the exception's class name in the logs with every exception that bubbles up to become a 500 error, I thought that maybe stacktraces contain slightly less info since we move to Kotlin. Probably not true. Just a thought. Maybe I'm mistaken and we never were able to see the class name of the exception in the logs on 500s. |
I'm not sure where things changed, but I seem to remember that I could see the class (
e::class.getSimpleName()
) of an exception in the logs. Currently it is gone.Therefor I want to change this line:
into:
In the following files:
Without objections I'll create a PR. Suggestions welcome, as always, on how to make it even better.
The text was updated successfully, but these errors were encountered: