logstash-input-udp 3.4.0 → 3.4.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7a0fb9a937142e05b98fc060e13c1c6dd02088c45585698a630368babe7b24c9
-  data.tar.gz: 4b81d1e42dc10ef2a18d351312f7e922203b56c491eeaef3200ca03992b2b0f6
+  metadata.gz: 2ba03e1c77b42ddb3277f9c32257c802e816f9b3f66beb01c6324f07ef10a304
+  data.tar.gz: f06690123677ae1de68260cf64f74cbeee29feaf9499f99b253266a158bb6fdf
 SHA512:
-  metadata.gz: c7e2011e1a7ffc850c20382636dd6f3c93596a1db20106fe1e13aab52494860cf9beb6a6ad5f8af563b39555a0791b52df6d0d333ab2b649c5869168a71ea93d
-  data.tar.gz: 90cb4afce18de5c517893565a907a64f770eeca401756a50eaa2885342cac702f344be120d6425d868b187c0529c7aee973d0d6ec574ae5f322f1c3517787a78
+  metadata.gz: 82c728db25566d1203afc8c40afe4a5f67e7c7852fc1e24c1eec85c041b7dc8523516a2a9fe58af7e07c7c0487b877616cff50bc00b1592bfe7086329aad1418
+  data.tar.gz: 69cc686c2464cd43e16c2ce9d5447fde7309485cbac54c4be78e1727423ac5eab317c9f603aa4c828747e1e5f4c24c3c5d0d2f14d3a80f340adfb8a8a735a34e

data/CHANGELOG.md

@@ -1,3 +1,6 @@
+## 3.4.1
+  - [DOC] Fixed typo in code sample [#54](https://github.com/logstash-plugins/logstash-input-udp/pull/54)
+
 ## 3.4.0
   - Added ECS compatibility mode (`disabled` and `v1`) to rename ip source address in a ECS compliant name [#50](https://github.com/logstash-plugins/logstash-input-udp/pull/50)
   - Fixed integration tests for IPv6 downgrading Docker to version 2.4 [#51](https://github.com/logstash-plugins/logstash-input-udp/pull/51)

data/docs/index.asciidoc

@@ -31,8 +31,9 @@ will listen on for event streams.
 
 This plugin adds a field containing the source IP address of the UDP packet.
 By default, the IP address is stored in the host field.
-When ECS is enabled (in <<plugins-{type}s-{plugin}-ecs_compatibility>>), the
-source IP address is stored in the [host][ip] field.
+When {ecs-ref}[Elastic Common Schema (ECS)] is enabled (in
+<<plugins-{type}s-{plugin}-ecs_compatibility>>), the source IP address is stored
+in the [host][ip] field.
 
 You can customize the field name using the <<plugins-{type}s-{plugin}-source_ip_fieldname>>.
 See <<plugins-{type}s-{plugin}-ecs_compatibility>> for more information.
@@ -80,7 +81,8 @@ The maximum packet size to read from the network
 ** When Logstash provides a `pipeline.ecs_compatibility` setting, its value is used as the default
 ** Otherwise, the default value is `disabled`.
 
-Controls this plugin's compatibility with the https://www.elastic.co/guide/en/ecs/current/index.html[Elastic Common Schema (ECS)].
+Controls this plugin's compatibility with the {ecs-ref}[Elastic Common Schema (ECS)].
+
 The value of this setting affects the placement of a TCP connection's metadata on events.
 
 .Metadata Location by `ecs_compatibility` value
@@ -142,7 +144,7 @@ Example:
 [source,ruby]
     input {
       udp {
-        source_ip_fieldname => "[appliace][monitoring][ip]"
+        source_ip_fieldname => "[appliance][monitoring][ip]"
       }
     }
 

data/logstash-input-udp.gemspec

@@ -1,7 +1,7 @@
 Gem::Specification.new do |s|
 
   s.name            = 'logstash-input-udp'
-  s.version         = '3.4.0'
+  s.version         = '3.4.1'
   s.licenses        = ['Apache License (2.0)']
   s.summary         = "Reads events over UDP"
   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-input-udp
 version: !ruby/object:Gem::Version
-  version: 3.4.0
+  version: 3.4.1
 platform: ruby
 authors:
 - Elastic
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2021-02-08 00:00:00.000000000 Z
+date: 2021-03-26 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   requirement: !ruby/object:Gem::Requirement