fluent-plugin-amplitude 0.0.5 → 0.0.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: ce23650ea41be224d3c3cace3bc46ecd231868e7
-  data.tar.gz: 9c51f42644f97118db2ff87001d9109d118a0f6a
+  metadata.gz: f9bc268ffa0a2a2c5702b54999f37d32fc32efcb
+  data.tar.gz: acdfb55e9cee0b966abd6de62397aa0bc568e875
 SHA512:
-  metadata.gz: bdfe8433824bbed0fc3eaf4f84d625c54f1a8262b541d11730d28939a857c4e834320dfac4414131cf0501e21401f9c131e93cbc7667ff14e3bcc977132f22ac
-  data.tar.gz: da8cda4768e715a4cbfd58f4acc18029b35677a5d8e1c2cd19141d7d8aa2e2275022111b4a685d49ee43951714f427d59cd4628c2a1d6c59900f26721a045b29
+  metadata.gz: 3a6bc77c06db97d7c6400298a6ab3b32aba7eca8ab93e92c1c6a6e2eefcf6e2624a1ec23ddaf97c4753d94c52833244a929a8722798ca3969016c2c739dbce94
+  data.tar.gz: 56bc85e14ef038f6018dae12b4e5a3ec61ab6c24e8cbb435cbd3e465ded69e9ac787aa6174db0f741f9e1007b38bcdc0c42f781805e63cbc8aeaf4c0f24fad8e

data/README.md

@@ -27,6 +27,7 @@ $ sudo /usr/lib64/fluent/ruby/bin/fluent-gem install fluent-plugin-amplitude
   event_properties current_source
   properties_blacklist user
   events_whitelist petition_view, petition_share
+  events_blacklist email_send
   flush_interval 5s
   retry_limit 2
   remove_tag_prefix output.amplitude.
@@ -66,6 +67,9 @@ Any properties included in the blacklist will be scrubbed from the record.
 #### events_whitelist
 If your `<match>` is using a wildcard, you can specify specific events to whitelist. If the `events_whitelist` is empty all events will be sent to Amplitude. Note the event name here is the `event_type` (so should not include, e.g., any prefixes that were removed via `remove_tag_prefix`)
 
+#### events_blacklist
+If your `<match>` is using a wildcard, you can specify specific events to blacklist. If the `events_blacklist` is empty all events will be sent to Amplitude. Note the event name here is the `event_type` (so should not include, e.g., any prefixes that were removed via `remove_tag_prefix`). It probably only makes sense to use `events_whitelist` or `events_blacklist`.
+
 #### Error handling
 Any error will result in the message retrying. In the case of an incorrectly configured API key, this can result in the messages infinitely retrying.  You should set the normal [buffered output plugin options](http://docs.fluentd.org/articles/buffer-plugin-overview) to prevent this (and to preserve data in the case of misconfigured records failing to be submitted to Amplitude).
 

data/fluent-plugin-amplitude.gemspec

@@ -4,7 +4,7 @@ $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
 
 Gem::Specification.new do |spec|
   spec.name          = 'fluent-plugin-amplitude'
-  spec.version       = '0.0.5'
+  spec.version       = '0.0.6'
   spec.authors       = ['Vijay Ramesh']
   spec.email         = ['vijay@change.org']
   spec.summary       = 'Fluentd plugin to output event data to Amplitude'

data/lib/fluent/plugin/out_amplitude.rb

@@ -14,6 +14,7 @@ module Fluent
     config_param :event_properties, :array, default: nil
     config_param :properties_blacklist, :array, default: nil
     config_param :events_whitelist, :array, default: nil
+    config_param :events_blacklist, :array, default: nil
     class AmplitudeError < StandardError
     end
 
@@ -38,6 +39,7 @@ module Fluent
 
     def format(tag, time, record)
       return if @events_whitelist && !@events_whitelist.include?(tag)
+      return if @events_blacklist && @events_blacklist.include?(tag)
 
       amplitude_hash = { event_type: tag }
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: fluent-plugin-amplitude
 version: !ruby/object:Gem::Version
-  version: 0.0.5
+  version: 0.0.6
 platform: ruby
 authors:
 - Vijay Ramesh
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-11-16 00:00:00.000000000 Z
+date: 2016-11-17 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: fluentd