As part of the Overlord BAM project I have an example integration with switchyard that registers an exchange handler as a means of intercepting messages sent and received by the service components.

As discussed here (https://community.jboss.org/thread/198945?tstart=30) it would be useful for the exchange handler to understand when an exchange has either originated or is destined for a binding, to avoid producing unnecessary 'message sent/received' events. These events are unnecessary when a binding is involved, as the binding only represents a gateway to the actual service that has 'sent' or 'received' the message - and it is the activity event from that external service that is actually required.

An alternative mechanism to the event handler approach has also been discussed, using the event notification mechanism that is currently used for collecting service metrics in switchyard. If this alternate mechanism is used instead of an event handler, for reporting activity events to the BAM infratructure, then the same context information regarding whether the source/target is a binding, would be required.