diff --git a/eip-wire-tap/README.md b/eip-wire-tap/README.md
new file mode 100644
index 000000000..d2742aa31
--- /dev/null
+++ b/eip-wire-tap/README.md
@@ -0,0 +1,29 @@
+---
+layout: pattern
+title: EIP Wire Tap
+folder: eip-wire-tap
+permalink: /patterns/eip-wire-tap/
+categories: Enterprise integration
+tags:
+ - Java
+ - Difficulty-Intermittent
+ - Enterprise integration
+---
+
+## Intent
+In most integration cases there is a need to monitor the messages flowing through the system. It is usually achieved
+by intercepting the message and redirecting it to a different location like console, filesystem or the database.
+It is important that such functionality should not modify the original message and influence the processing path.
+
+![alt text](./etc/wiretap.gif "Wire Tap")
+
+## Applicability
+Use the Wire Tap pattern when
+
+* You need to monitor messages flowing through the system
+* You need to redirect the same, unchanged message to two different endpoints/paths
+
+## Credits
+
+* [Gregor Hohpe, Bobby Woolf - Enterprise Integration Patterns](http://www.enterpriseintegrationpatterns.com/patterns/messaging/WireTap.html)
+* [Apache Camel - Documentation](http://camel.apache.org/wire-tap.html)
diff --git a/eip-wire-tap/etc/wiretap.gif b/eip-wire-tap/etc/wiretap.gif
new file mode 100644
index 000000000..414173716
Binary files /dev/null and b/eip-wire-tap/etc/wiretap.gif differ