Scenario 1 (Blacklisted Entry-point)

Exception StackTrace

The entry-point of the call stack is part of a blacklisted class/library.

a             throws the exception
b
c             is blacklisted
d 
e             is blacklisted  entry point

OverOps View

In OverOps that blacklisted class is skipped and the next class in the call stack is shown as entry-point.

a             throws the exception
b
d             as the entry point

Scenario 2 (Blacklisted Exception)

Exception StackTrace

The class which throws the exception is blacklisted or part of a blacklisted library.

a            blacklisted  throws exception
b 
c            blacklisted
d            catches it
e 
f            blacklist entry point

OverOps view

As in Scenario 1, the blacklisted class is skipped and the next class in the stack is shown as the class having thrown the exception.

b            throws exception
d            catches it 
e            entry point

Scenario 3 (Blacklisted exception and catch frame)

Exception StackTrace

Here both the class which throws the exception and the class which catches the exception are blacklisted.

a            blacklisted throws exception
b 
c            blacklisted 
d            blacklisted catches it
e 
f            entry point

OverOps

❗️

We do not capture these events.

Scenario 4 (blacklisted catch frame but no blacklisted exception)

Exception StackTrace

Here the class which catches the exception is blacklisted.

a            throws exception
b
c            blacklisted
d            blacklisted catches it
e
f            blacklist entry point

OverOps view

In OverOps the class which catches the exception is not shown!

b            throws exception
e            Entry Point

👍

A message is provided which will tell you the exception was caught in 3rd party class.
You will need to toggle the Show 3rd party/utility methods switch to see the capture icon and the actual 3rd party class in the stack trace view.

Log Events

These rules also apply to log events.
For example, the actual logging utility class which creates the log event is blacklisted (Best practice) which will cause that Overops skips that class and the next "meaningful" class will be shown in Overops, not the logging utility class.