Allatori can be easily configured to do the following:

1. Leave debug information without modifications.
Helpful for internal testing of your application. In other cases it's better to choose other options.

The stack trace will be reported like the following:

java.lang.NullPointerException
        at com.company.c.a(Util.java:38)
        at com.company.b.b(TraceTest.java:53)
        at com.company.b.a(TraceTest.java:14)
        at com.company.a.a(Main.java:27)

2. Remove debug information.
This option can be used when the size of your application matters; by removing debug information you can save a considerable amount of space.

The stack trace will be reported like the following:

java.lang.NullPointerException
        at com.company.c.a(Unknown Source)
        at com.company.b.b(Unknown Source)
        at com.company.b.a(Unknown Source)
        at com.company.a.a(Unknown Source)

3. Substitute (obfuscate) debug information.
Debug information remains, but it's obfuscated, and so the use of it without transforming simply stupefies the hacker. In this case it is absolutely impossible to understand where the exception has taken place. But Allatori has a special utility which allows reconstruction of the original stack trace with the help of a substituted one. Substitution of debug information shrinks the application and doesn't affect productivity at all, so it is desirable to use this option in the majority of cases.

The stack trace will be reported like the following:

java.lang.NullPointerException
        at com.company.c.a(m:61)
        at com.company.b.b(w:94)
        at com.company.b.a(w:83)
        at com.company.a.a(n:75)