fluent-plugin-systemd 1.0.0 → 1.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 05b2387f068e7c0ec23f74f61bb5d1b031fbd670
-  data.tar.gz: 438b9f07ea3b23d6af05077ec460f51e413002e4
+  metadata.gz: c6e9aac538e4ec4e1a65dae4873493e2439b8b59
+  data.tar.gz: f6589478860a0b2864929339651005df1732d9b0
 SHA512:
-  metadata.gz: 23d0e490a9befa2d01ea8fd6092dbed234ea8a31e3433cb458a584195d0ba6a08376881641df75db4fb139887e869b66c935a58ce7daf796d24bea8b533020fa
-  data.tar.gz: 7ac5767e188b7ef944c62415a7e13eb100effa83f05784377b7fa071b9a6cbc52eaf72f7f45a5d593d0302474e4ca858d746a616ae1ec2a8522c62f20cc09dc8
+  metadata.gz: d0efddc0d59ca876d8b7cd356dd9f238b99eb5d6c55cd2fee5ae65e26bceeea9d6f61afbcc1f5b17e1eed891fc30f744a81bd01a7ef475b62db821a1415a6018
+  data.tar.gz: 7613bdc750bab5a6738e27540aa30ce55affa625614c9b848302995ef642adc41250c091f16f1eecd80193940d281e118977416dcf4ada17fe4ca0eccb709340

data/README.md

@@ -28,11 +28,11 @@ Join the #plugin-systemd channel on the [Fluentd Slack](http://slack.fluentd.org
 
 Simply use RubyGems:
 
-    gem install fluent-plugin-systemd -v 1.0.0
+    gem install fluent-plugin-systemd -v 1.0.1
 
 or
 
-    td-agent-gem install fluent-plugin-systemd -v 1.0.0
+    td-agent-gem install fluent-plugin-systemd -v 1.0.1
 
 ## Upgrading
 
@@ -186,6 +186,16 @@ Another strategy would be to use a plugin like [fluent-plugin-concat](https://gi
 * You can use an [offical fluentd docker](https://github.com/fluent/fluentd-docker-image) image as a base, (choose the debian based version, as alpine linux doesn't support systemd).
 * Bind mount `/var/log/journal` into your container.
 
+> ### I am seeing lots of logs being generated very rapidly!
+
+This commonly occurs when a loop is created when fluentd is logging to STDOUT, and the collected logs are then written to the systemd journal. This could happen if you run fluentd as a systemd serivce, or as a docker container with the systemd log driver.
+
+Workarounds include:
+
+* Use another fluentd output
+* Don't read every message from the journal, set some `matches` so you only read the messages you are interested in.
+* Disable the systemd log driver when you launch your fluentd docker container, e.g. by passing `--log-driver json-file`
+
 ### Example
 
 For an example of a full working setup including the plugin, take a look at [the fluentd kubernetes daemonset](https://github.com/fluent/fluentd-kubernetes-daemonset)

data/lib/fluent/plugin/in_systemd.rb

@@ -66,9 +66,6 @@ module Fluent
         # TODO: ruby 2.3
         @journal.close if @journal # rubocop:disable Style/SafeNavigation
         @journal = Systemd::Journal.new(path: @path)
-        # make sure initial call to wait doesn't return :invalidate
-        # see https://github.com/ledbettj/systemd-journal/issues/70
-        @journal.wait(0)
         @journal.filter(*(@matches || @filters))
         seek
         true

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: fluent-plugin-systemd
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.0.1
 platform: ruby
 authors:
 - Ed Robinson
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-05-10 00:00:00.000000000 Z
+date: 2018-06-12 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -92,14 +92,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.3'
+        version: 1.3.2
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.3'
+        version: 1.3.2
 description: This is a fluentd input plugin. It reads logs from the systemd journal.
 email:
 - edward-robinson@cookpad.com