In some recording, they begin with a long period where the only events are things like
Socket Read, Java Wait, etc, until you get events like CPU Load and others.
In my example recording, this period is 90% of the recording (event span) time.

This make it harder to visualize the interesting part of the recording, and makes it harder for the rules that measure things correctly

We should be able to heuristically detect when this occurs, and filter out this period from rules.
We could also filter them out in the UI, optional for the user.

JMC-5505 has another solution for this, but until that is solved in the JDK, I think would be useful.