A question about stack traces

[froderick]

Hi,

I was an hour into writing something very much like this, when I happened on yours! One of the things that's kept me from embracing json logging in the past was dealing with hard-to-read stacktraces. Especially in clojure, where they tend to be huge. I'm curious, how do you work with stack trace outputs from this library? Did you write some formatting code that you run on the output to make it easier to read when needed, or did you just learn to read the matrix? :)

Thanks

[viesti]

Ha, I guess I learned to love the matrix :D Actually, at dev time I use plain println appender and in production, I sometimes tend to pipe to jq e.g. awslogs get -f Exception -S -G backend | jq.

I have been thinking about a formatter, that would output links to source code (and do a bit more compact formatting), so one could jump to the source by cmd-click in iTerm, or maybe it could be possible to register a custom handler, that would open the file into editor with cursor on the line number (https://www.iterm2.com/smartselection.html).

Writing utility like that in babashka would make it fast to use even.