logstash-filter-json 3.0.5 → 3.0.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 901cffe5a5ce6505bf2f526f1d2dff7ed383bf49decc13517e7ce2a79dee0f5b
-  data.tar.gz: 1f03087447ff7e5d7ea36730fc51982aa73558fdbfe7365e3241d05d442b8309
+  metadata.gz: 2ddf0449d8e4b3c20ad42da931a88623695222c346815463d100f184deb39a41
+  data.tar.gz: bd1c0786156077172f52eb2998b86030ec8524ed341a8b17544942f5b662f69e
 SHA512:
-  metadata.gz: ceda74bfd5767ef968e1b953f9b025bfb6438c6aa3a857fd1a69f7b02b26ca3b0ae1f9205a976530fc432af61eb57cc73665da326a4d7942009ad02783c00763
-  data.tar.gz: 38b27202d86da5e77fc171d1d3c3b7c9e417ac9c931a77946c4522a28154e498aed1a09d48f6778b58f9e8acd41c3ba1bbb947e70443ae8afb2cbe3d1d10847c
+  metadata.gz: 191f3b6b17ae2d93c10d763fbe765bead21e1e6932986dd188a493d5e616245f2d9e6ec1956b3fbe29edfa9e3aa98a828d803b51fd12a18bd6fa860f26813700
+  data.tar.gz: 0a7189b4d3249b2a249b263c5fdfe0180b164f633fa2d90a1ec9d979cbdd0e9b18a02ff3fd92e9addc351699188074e93bea1ef43630ac42e4b6d5aa8c6b597c

data/CHANGELOG.md

@@ -1,3 +1,6 @@
+## 3.0.6
+  - Updated documentation with some clarifications and fixes
+
 ## 3.0.5
   - Update gemspec summary
 

data/LICENSE

@@ -1,4 +1,4 @@
-Copyright (c) 2012–2016 Elasticsearch <http://www.elastic.co>
+Copyright (c) 2012-2018 Elasticsearch <http://www.elastic.co>
 
 Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.

data/docs/index.asciidoc

@@ -14,7 +14,7 @@ END - GENERATED VARIABLES, DO NOT EDIT!
 
 [id="plugins-{type}s-{plugin}"]
 
-=== Json filter plugin
+=== JSON filter plugin
 
 include::{include_path}/plugin_header.asciidoc[]
 
@@ -23,21 +23,21 @@ include::{include_path}/plugin_header.asciidoc[]
 This is a JSON parsing filter. It takes an existing field which contains JSON and
 expands it into an actual data structure within the Logstash event.
 
-By default it will place the parsed JSON in the root (top level) of the Logstash event, but this
+By default, it will place the parsed JSON in the root (top level) of the Logstash event, but this
 filter can be configured to place the JSON into any arbitrary event field, using the
 `target` configuration.
 
-This plugin has a few fallback scenario when something bad happen during the parsing of the event.
-If the JSON parsing fails on the data, the event will be untouched and it will be tagged with a
-`_jsonparsefailure` then you can use conditionals to clean the data. You can configured this tag with then
+This plugin has a few fallback scenarios when something bad happens during the parsing of the event.
+If the JSON parsing fails on the data, the event will be untouched and it will be tagged with
+`_jsonparsefailure`; you can then use conditionals to clean the data. You can configure this tag with the
 `tag_on_failure` option.
 
-If the parsed data contains a `@timestamp` field, we will try to use it for the event's `@timestamp`, if the
+If the parsed data contains a `@timestamp` field, the plugin will try to use it for the events `@timestamp`, and if the
 parsing fails, the field will be renamed to `_@timestamp` and the event will be tagged with a
 `_timestampparsefailure`.
 
 [id="plugins-{type}s-{plugin}-options"]
-==== Json Filter Configuration Options
+==== JSON Filter Configuration Options
 
 This plugin supports the following configuration options plus the <<plugins-{type}s-{plugin}-common-options>> described later.
 
@@ -61,7 +61,7 @@ filter plugins.
   * Value type is <<boolean,boolean>>
   * Default value is `false`
 
-Allow to skip filter on invalid json (allows to handle json and non-json data without warnings)
+Allows for skipping the filter on invalid JSON (this allows you to handle JSON and non-JSON data without warnings)
 
 [id="plugins-{type}s-{plugin}-source"]
 ===== `source` 
@@ -82,7 +82,7 @@ For example, if you have JSON data in the `message` field:
       }
     }
 
-The above would parse the json from the `message` field
+The above would parse the JSON from the `message` field.
 
 [id="plugins-{type}s-{plugin}-tag_on_failure"]
 ===== `tag_on_failure` 
@@ -118,4 +118,4 @@ NOTE: if the `target` field already exists, it will be overwritten!
 
 
 [id="plugins-{type}s-{plugin}-common-options"]
-include::{include_path}/{type}.asciidoc[]
+include::{include_path}/{type}.asciidoc[]

data/logstash-filter-json.gemspec

@@ -1,7 +1,7 @@
 Gem::Specification.new do |s|
 
   s.name            = 'logstash-filter-json'
-  s.version         = '3.0.5'
+  s.version         = '3.0.6'
   s.licenses        = ['Apache License (2.0)']
   s.summary         = "Parses JSON events"
   s.description     = "This gem is a Logstash plugin required to be installed on top of the Logstash core pipeline using $LS_HOME/bin/logstash-plugin install gemname. This gem is not a stand-alone program"

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: logstash-filter-json
 version: !ruby/object:Gem::Version
-  version: 3.0.5
+  version: 3.0.6
 platform: ruby
 authors:
 - Elastic
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2017-11-07 00:00:00.000000000 Z
+date: 2019-02-04 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   requirement: !ruby/object:Gem::Requirement
@@ -84,7 +84,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project:
-rubygems_version: 2.6.11
+rubygems_version: 2.6.13
 signing_key:
 specification_version: 4
 summary: Parses JSON events