logstash-filter-wurfl_device_detection 0.3.4 → 0.4.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f636e0ec48c5431a30aa59f1e1e85191ab2985639f18cc8ce1b30b38c325e0b3
-  data.tar.gz: 626f1dfae8bab9d541d72850c5d6f34831c92f8a3ad4ce7f604e0dbd2371335f
+  metadata.gz: 2168139619cce611e9e955b5f3eb575cbb3720699137ff83e7706af4c92b7c4c
+  data.tar.gz: 005aa079e3e9b0d7fdf0a46ca83e604f23a89a10769d202d0baf828078eb82af
 SHA512:
-  metadata.gz: 42aff0f5139a4215f724479ba1d11bb17c5fb9e0a690580a07cbf950acf0c9186882ae16dc8939a5433c2d1245cf7f9374c9a23149048db7faf05defe7c5ca2e
-  data.tar.gz: c8cf61ba8d3405e3016458233cb83f0ea12d7f7fc57817bf0ebc4a69864cfdf105dff50221ea4051759a5ee35cd692f0aa9a29e8247aab0b5c304caacae1551c
+  metadata.gz: 4f763e50ca546c2167fc1b5d89ccce4e628170ccb6f331448765b922ad0a386962dd1ad785a69e78bcbae99cd764b84faf46d621f35cdc63723e14724c9b1ab6
+  data.tar.gz: d21a9e70ee6981d3f8659e6bfe313516a177706a299eb63c6410e3188f65d17f978b631aeafc59005c7ba5598d28d02bac5aef69c4a16766180a4ad55261ec17

data/CHANGELOG.md

@@ -1,3 +1,5 @@
+- 0.4.0 - now support for array of events
+
 - 0.3.4 - added gemspec file, fixed naming convention issues
 
 - 0.3.3 - Better description of WM pre requisites in rubygem.org deploy

data/README.md

@@ -46,11 +46,57 @@ output {
   stdout { codec => rubydebug }
 }
 ```
+
+The http input plugin receives an http request to the specified host and port, with a payload map that contains the HTTP headers that the WURFL plugin will analyze.
+Note that the `source` name is `headers`. Also note that you can configure the logstash input as you want,
+but if you want the WURFL plugin to work with headers, you must configure it so that it uses an header map.
+
+### Example configuration - using JSON input and filter plugins to receive HTTP request data
+Scenario: we configure logstash to receive HTTP request information from one or more JSON files (needs logstash-filter-json plugin).
+
+```
+input {
+  file {
+    type => "json"
+    path => "<path to>/logstash-filter-wurfl/sample_input/kafka_events_mini.json"
+    start_position => "beginning"
+  }
+}
+filter {
+    json {
+    source => "message"
+}
+}
+filter {
+  wurfl_device_detection {
+    source => "message"
+    cache_size => 300000
+    inject_wurfl_id => true
+    inject_wurfl_info => false
+    inject_wurfl_api_version => false
+    # commenting the capabilities config, you get them all
+    #static_capabilities => ["model_name", "brand_name"]
+    #virtual_capabilities => ["form_factor"]
+    scheme => "http"
+    host => "localhost"
+    port => "8080"
+  }
+}
+output {
+  # you may choose whatever output you want
+  stdout { codec => rubydebug }
+}
+```
+
+Source field "message" is the root element of the json file
+
+### Starting logstash
+
 Start the WURFL Microservice server on AWS/Azure/Docker then, let's run logstash:
 
 `./logstash -f <path_to_configuration>.conf>`
 
-sending a HTTP request to its configured port (in this case 19080) like this (we just add the user-agent header for simplicity):
+in case you choose the HTTP input configuration, sending a HTTP request to its configured port (in this case 19080) like this (we just add the user-agent header for simplicity, but you can send all headers using the -H flag):
 
 `curl -H "User-Agent: Mozilla/5.0 (Linux; Android 8.0.0; Pixel 2 XL Build/OPD1.170816.004) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3359.139 Mobile Safari/537.36" http://localhost:19080`
 
@@ -105,9 +151,7 @@ we'll get an output that looks like this:
 
 ```
 
-The http input plugin receives an http request to the specified host and port, with a payload map that contains the HTTP headers that the WURFL plugin will analyze.
-Note that the `source` name is `headers`. Also note that you can configure the logstash input as you want,
-but if you want the WURFL plugin to work with headers, you must configure it so that it uses an header map.
+In case you chose the JSON input file configuration, logstash will automatically parse it and print the output.
 
 - `stdin` and `stdout` define which input and output plugin will be used:  in our scenario
  we use the HTTP input plugin, while we use the ruby debug console as output.

data/VERSION

@@ -1 +1 @@
-0.3.4
+0.4.0

data/lib/logstash-filter-wurfl_device_detection_jars.rb

@@ -2,4 +2,4 @@
 # encoding: utf-8
 
 require 'jar_dependencies'
-require_jar('com.scientiamobile.logstash', 'logstash-filter-wurfl_device_detection', '0.3.4')
+require_jar('com.scientiamobile.logstash', 'logstash-filter-wurfl_device_detection', '0.4.0')

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: logstash-filter-wurfl_device_detection
 version: !ruby/object:Gem::Version
-  version: 0.3.4
+  version: 0.4.0
 platform: ruby
 authors:
 - ScientiaMobile Inc.
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2020-09-07 00:00:00.000000000 Z
+date: 2020-09-23 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   requirement: !ruby/object:Gem::Requirement
@@ -79,7 +79,7 @@ files:
 - lib/logstash-filter-wurfl_device_detection_jars.rb
 - lib/logstash/filters/wurfl_device_detection.rb
 - logstash-filter-wurfl_device_detection.gemspec
-- vendor/jar-dependencies/com/scientiamobile/logstash/logstash-filter-wurfl_device_detection/0.3.4/logstash-filter-wurfl_device_detection-0.3.4.jar
+- vendor/jar-dependencies/com/scientiamobile/logstash/logstash-filter-wurfl_device_detection/0.4.0/logstash-filter-wurfl_device_detection-0.4.0.jar
 homepage: http://www.scientiamobile.com
 licenses:
 - Apache-2.0