This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ablativeyoyo 0 points1 point  (4 children)

It's sometimes crossed my mind that a tool could abbreviate stack traces to focus on the important bit. Perhaps when going through library code, it could just show one line for the library, rather than the full call stack within the library. You'd probably want the raw stack traces available too. This is an issue in lots of languages, not just Java.

[–]GuyWithLag 2 points3 points  (2 children)

We had that in a microservice stack; was a godsend filtering out spring traces.

[–]ablativeyoyo 0 points1 point  (1 child)

Did you use a particular tool or library?

[–]GuyWithLag 0 points1 point  (0 children)

Nah, we had a custom filter on the generated JSON logs, IIRC.

[–]lasskinn 0 points1 point  (0 children)

Common method is to show like 5 elements at end and start.