For example, Throwables.getRootCause (Throwable) returns the exception that is often most important (see Tips #2 and #3 in Ten Tips for Using Java Stack Traces) in a chain (the “innermost” or ...

Fortunately, two of the most popular Java logging frameworks, java.util.logging and log4j, provide convenient methods for logging exceptions that will handle the stack trace information automatically.

Because an event in Sentry can have multiple exceptions, and each exception can have multiple stack frames, the first two are fairly ambiguous. What is the matching strategy when using path or module?