Depends on and cross JVM Tracing.
Specify and implement generic diagnosis rules that occure in cross JVM invocation sequences. Example: The invocation sequences of each single JVM show no real problems but regardless of this is the cross JVM invocation sequences is to slow. (slower than a predefined threshold)
I understand this as a new layer in the analysis process. We can now say that something (from the view of the enduser/BT) was slow and can then tell that this was more components, just one component, the link between components, ... So the analyst/end user of inspectIT can get information that is was - for example - always the link between component A and B that was responsible for the problem.