Merge branch 'master' of https://github.com/Axway-API-Management-Plus/apigateway-openlogging-elk

Author: Chris Wiechmann

README.md

@@ -5,9 +5,12 @@ When having many API-Gateway instances with millions of requests the API-Gateway
 The overall architecture this project provides looks like this:  
 ![Architecture][img1]   
 
-This also makes it possible to collect data from API-Gateways running all over the world into a centralized Elasticsearch instance to have it available with the best possible performance independing from the network performance.  
+This also makes it possible to collect data from API-Gateways running all over the world into a centralized Elasticsearch instance to have it available with the best possible performance indendent from the network performance.  
 It also helps, when running the Axway API-Gateway in Docker-Orchestration-Environment where containers are started and stopped as it avoids to loose data, when an API-Gateway container is stopped.  
 
+Watch this video to see a side by side compare betwen the classical and ElasticSearch based Traffic-Monitor:  
+[![API-Management CLI](https://img.youtube.com/vi/MUbx4m9EtpY/0.jpg)](https://youtu.be/MUbx4m9EtpY)
+
 ### How it works  
 Each API-Gateway instance is writing, [if configured](#enable-open-traffic-event-log), Open-Traffic Event-Log-Files, which are streamed by [Filebeat](https://www.elastic.co/beats/filebeat) into a Logstash-Instance. [Logstash](https://www.elastic.co/logstash) performs data pre-processing, combines different events and finally forwards these so called documents into an Elasticsearch cluster.