Improve logging for Direct Call Rules (and maybe custom events?)

[#1]

It'd be great if when _satellite.setDebug(true) were enabled, you would get additional information about the _satellite.track functions and Custom Events that are firing. I described an external workaround/fix in a blog post (Enhanced logging for Direct Call Rules and Custom Events for Launch/DTM - 33 Sticks ) but basically, right now for a Direct Call Rule I can either know it fired, or its string wasn't found as a Direct Call Rule trigger:

But now that folks can send extra params with more information, it'd be great to see more details- something like this:

Something like this would also be wonderful for Custom Events, though I understand that would be trickier because Custom Events are far more, well, custom- I'm not sure how you would listen to them if they can have any name and be bound to any DOM object- but that would be very helpful.

[#2]

Also pointing out that this data would be nice to have in the monitor events.