Check Point: fw monitor - How To Debug Packets Through The Firewall In CLI

I was on a TAC call today with Check Point, and "I" was troubleshooting a RADIUS issue while "TAC" was troubleshooting a firewall rule issue.  Check Point TAC's first line of support is terrible, but I digress.  I did, however, learn something interesting today about debugs.  The TAC guy was trying to see, in CLI, if packets were actually getting through the firewall.  So, he ran this command in expert mode:
[Expert@VPN1]# fw monitor -e "accept src=209.217.70.2 or dst=209.217.70.2;"

Now, here is what was interesting.  We ran a ping from my switch in the inside of the network, behind the firewall, and got these results in the CLI (shortened, but you get the idea):
 monitor: getting filter (from command line)
 monitor: compiling
monitorfilter:
Compiled OK.
 monitor: loading
 monitor: monitoring (control-C to stop)
[fw_0] Lan1:i[100]: 10.50.1.254 -> 209.217.70.2 (ICMP) len=100 id=363
ICMP: type=8 code=0 echo request id=1189 seq=8192
[fw_0] Lan1:I[100]: 10.50.1.254 -> 209.217.70.2 (ICMP) len=100 id=363
ICMP: type=8 code=0 echo request id=1189 seq=8192
[fw_0] Lan5:o[100]: 10.50.1.254 -> 209.217.70.2 (ICMP) len=100 id=363
ICMP: type=8 code=0 echo request id=1189 seq=8192
[fw_0] Lan5:O[100]: 10.50.1.254 -> 209.217.70.2 (ICMP) len=100 id=363
ICMP: type=8 code=0 echo request id=1189 seq=8192
[fw_0] Lan1:i[100]: 10.50.1.254 -> 209.217.70.2 (ICMP) len=100 id=364
ICMP: type=8 code=0 echo request id=1190 seq=8192
[fw_0] Lan1:I[100]: 10.50.1.254 -> 209.217.70.2 (ICMP) len=100 id=364

So, I asked what some of this means, and I found that there is some really good troubleshooting techniques in this.  Here is what was explained to me:

Pretty cool stuff.