Hey Mr Kuma, the link does define the problem at it's core. My question might be too broad because I don't have any evidence that appD would or could not discover an object causing a cartesian product. The better question is not whether the offending object can be observed or is it being excluded by default. Also if I could include that object even if it is a caratesian product it might not be detected as a slow or very slow object based on the default standard deviation buckets. I might have to make the performance threshold really strict to force appD to instrument a BT it wouldn't otherwise pay attention too.
Hmm, what do you think? Is this kind of tweaking necessary or am I diggin in the wrong direction?
Thanks,
curtis