Let the business message continue through its normal route.
System Management
Wire Tap
Send a copy of each message to a secondary channel for observation while allowing the original message to continue unchanged.
How do you inspect messages that travel on a point-to-point channel?Adapted from Enterprise Integration Patterns under CC BY 3.0. The visualization and explanatory content on this page are original GateSift material.
Original GateSift visualization
How Wire Tap works
The normal flow continues while an additional operational or diagnostic view is produced.
Live message flow
Wire Tap
Primary destination
Operational insight
Apply Wire Tap without changing the intended business destination.
Capture trace, history, control or diagnostic information for operators.
What this pattern helps you decide
Send a copy of each message to a secondary channel for observation while allowing the original message to continue unchanged.
What happens when processing fails or the same message is delivered twice?
Where does state, correlation or routing configuration live?
How will operators trace the message and understand the decision path?
Where you may see it
- APIM/Event Hub logging fragment
- Service Bus topic audit subscription
- BizTalk tracking copy
How the analyzers can surface it
- Logging fragments and duplicate sends
- Observation channels
Pattern detection is contextual. GateSift should present these as architectural signals, not claim a pattern is implemented solely because one policy statement or adapter exists.
Source, licence and attribution
The pattern name and selected problem statement are adapted from Enterprise Integration Patterns by Gregor Hohpe and Bobby Woolf under CC BY 3.0. GateSift summaries, Azure mappings, analyzer guidance and diagrams are original. No endorsement by the original authors is implied.