logstash-input-syslog 3.4.2 → 3.4.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d63c76951bace8d2eb194fdac21771964da3a9e38b88e549b949754aa24c02f7
-  data.tar.gz: 5b137708c39d040d6ed0f38ea127874a7f0e894fb13004375ecf5b0a48b7569a
+  metadata.gz: dc9057a2c876b1bdb746a10c07fcc32b66d265aeb5658e1116fb0435bd29ea76
+  data.tar.gz: f33e03b2bb5cdad71d2152c6d563db6c2a1d7175e7cb24d6f5b872d707dbfc42
 SHA512:
-  metadata.gz: 29bdc435ac857f12e8ec9b8f74d986ff0be227bf09e4982aae764fae5925aa971a6154b1bc6a77201b2824a28484cf84639fd8553d336da5099ee014c2bec657
-  data.tar.gz: bbf847a0284ba65b81089d43132747ed94e9c89c734681cb3b48c9f81b07c519b6a710143216935cb645d875e5b52e49aa0a1e004c79d2c18adeb8fb8ec35f36
+  metadata.gz: 877bd6b44875b1b4318e08073d53caef55c90dbe636ab49a0e7c4e2af5d3c6f8a12527250e0988442aa12e884eee8902db89803cd0a517aa0506bb1127de4ea1
+  data.tar.gz: 477cd68ad7aedb6125205b4c88d0ec2bdae3e5e58d82bc91c21317eef919f1047b7c9d4bbc2ccc7e381c447d1af2adda0ed8d69585544fd95d0a65884af91abb

data/CHANGELOG.md

@@ -1,3 +1,6 @@
+## 3.4.3
+  - [DOC] Added expanded descriptions and requirements for facility_labels and severity_labels. [#52](https://github.com/logstash-plugins/logstash-input-syslog/pull/52)
+
 ## 3.4.2
   - Remove (deprecated) dependency on thread_safe gem.
   - CI: upgrade testing [#58](https://github.com/logstash-plugins/logstash-input-syslog/pull/58)

data/docs/index.asciidoc

@@ -70,7 +70,14 @@ input plugins.
   * Value type is <<array,array>>
   * Default value is `["kernel", "user-level", "mail", "system", "security/authorization", "syslogd", "line printer", "network news", "UUCP", "clock", "security/authorization", "FTP", "NTP", "log audit", "log alert", "clock", "local0", "local1", "local2", "local3", "local4", "local5", "local6", "local7"]`
 
-Labels for facility levels. These are defined in RFC3164.
+Labels for facility levels defined in RFC3164.
+
+You can use this option to override the integer->label mapping for syslog inputs
+that behave differently than the RFCs. 
+
+Provide a zero-indexed array with all of your facility labels _in order_.
+If a log message contains a facility number with no corresponding entry,
+the facility_label is not added to the event.
 
 [id="plugins-{type}s-{plugin}-grok_pattern"]
 ===== `grok_pattern`
@@ -136,7 +143,11 @@ http://www.haproxy.org/download/1.5/doc/proxy-protocol.txt
   * Value type is <<array,array>>
   * Default value is `["Emergency", "Alert", "Critical", "Error", "Warning", "Notice", "Informational", "Debug"]`
 
-Labels for severity levels. These are defined in RFC3164.
+Labels for severity levels defined in RFC3164.
+
+Provide a zero-indexed array with all of your severity labels _in order_.
+If a log message contains a severity label with no corresponding entry,
+the severity_label is not added to the event.
 
 [id="plugins-{type}s-{plugin}-syslog_field"]
 ===== `syslog_field`

data/logstash-input-syslog.gemspec

@@ -1,7 +1,7 @@
 Gem::Specification.new do |s|
 
   s.name            = 'logstash-input-syslog'
-  s.version         = '3.4.2'
+  s.version         = '3.4.3'
   s.licenses        = ['Apache License (2.0)']
   s.summary         = "Reads syslog messages as 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-input-syslog
 version: !ruby/object:Gem::Version
-  version: 3.4.2
+  version: 3.4.3
 platform: ruby
 authors:
 - Elastic
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2020-04-28 00:00:00.000000000 Z
+date: 2020-05-19 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   requirement: !ruby/object:Gem::Requirement