logstash-filter-metrics 4.0.1 → 4.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: d2a21882f3e38ec83d7674acc15ec05e716e8106
-  data.tar.gz: 69db446491315b1e2c64aa35589a8171c97f84bc
+  metadata.gz: 57bfe0e3b3d5fdd1ea24b7bad5576e6d1689e661
+  data.tar.gz: b2c9a453d532be098be076b6a3af4b1d8961645a
 SHA512:
-  metadata.gz: 5d14a3f89605a96a1da8ba160da5486c3a145d2803729e202e509d5d88fa51120ce5e2b9791599f15beaaebebc9fb02de76a8c73a90f7ec26c9d0d547dfd97ed
-  data.tar.gz: ff622a0ed01f86f764b070af13067032c0f48b550e4e78c937f0bcbb8f2b092e252eed50ea96855c9169ca6f3370a39a096e352ef607802593fe8e577ebcbe35
+  metadata.gz: 1e7521606f0700ae3c18af48c833f7eee82671ba9a4cdcebb2026eb38a74a106167350c64712bae09329783e64e042492eca94d351048d2e828c6374b6cb458e
+  data.tar.gz: 8ed0fdea1046750ca4c515f5ce5e28e765e5f8a35cc0d8854af697a61294f3fb36b9d5ee89ac58a37504fbcd2b421241918fd15deecb0b3edecec4c428548f5f

data/CHANGELOG.md

@@ -1,3 +1,6 @@
+## 4.0.2
+  - Relax constraint on logstash-core-plugin-api to >= 1.60 <= 2.99
+
 ## 4.0.1
   - Republish all the gems under jruby.
 ## 4.0.0

data/lib/logstash/filters/metrics.rb

@@ -10,7 +10,7 @@ require "logstash/namespace"
 # dotted notation to avoid colliding with versions of Elasticsearch 2.0+.  Please
 # note the changes in the documentation (underscores and sub-fields used).
 #
-# For example, if you have a field 'response' that is
+# For example, if you have a field `response` that is
 # a http response code, and you want to count each
 # kind of response, you can do this:
 # [source,ruby]
@@ -22,7 +22,7 @@ require "logstash/namespace"
 #     }
 #
 # Metrics are flushed every 5 seconds by default or according to
-# 'flush_interval'. Metrics appear as
+# `flush_interval`. Metrics appear as
 # new events in the event stream and go through any filters
 # that occur after as well as outputs.
 #
@@ -32,30 +32,33 @@ require "logstash/namespace"
 # The event that is flushed will include every 'meter' and 'timer'
 # metric in the following way:
 #
-# #### 'meter' values
+# ==== `meter` values
 #
 # For a `meter => "something"` you will receive the following fields:
 #
 # * "[thing][count]" - the total count of events
-# * "[thing][rate_1m]" - the 1-minute rate (sliding)
-# * "[thing][rate_5m]" - the 5-minute rate (sliding)
-# * "[thing][rate_15m]" - the 15-minute rate (sliding)
+# * "[thing][rate_1m]" - the per-second event rate in a 1-minute sliding window
+# * "[thing][rate_5m]" - the per-second event rate in a 5-minute sliding window
+# * "[thing][rate_15m]" - the per-second event rate in a 15-minute sliding window
 #
-# #### 'timer' values
+# ==== `timer` values
 #
 # For a `timer => [ "thing", "%{duration}" ]` you will receive the following fields:
 #
 # * "[thing][count]" - the total count of events
-# * "[thing][rate_1m]" - the 1-minute rate of events (sliding)
-# * "[thing][rate_5m]" - the 5-minute rate of events (sliding)
-# * "[thing][rate_15m]" - the 15-minute rate of events (sliding)
+# * "[thing][rate_1m]" - the per-second event rate in a 1-minute sliding window
+# * "[thing][rate_5m]" - the per-second event rate in a 5-minute sliding window
+# * "[thing][rate_15m]" - the per-second event rate in a 15-minute sliding window
 # * "[thing][min]" - the minimum value seen for this metric
 # * "[thing][max]" - the maximum value seen for this metric
 # * "[thing][stddev]" - the standard deviation for this metric
 # * "[thing][mean]" - the mean for this metric
 # * "[thing][pXX]" - the XXth percentile for this metric (see `percentiles`)
 #
-# #### Example: computing event rate
+# The default lengths of the event rate window (1, 5, and 15 minutes)
+# can be configured with the `rates` option.
+#
+# ==== Example: Computing event rate
 #
 # For a simple example, let's track how many events per second are running
 # through logstash:
@@ -96,7 +99,7 @@ require "logstash/namespace"
 #     rate: 25875.892745934525
 #     rate: 26836.42375967113
 #
-# We see the output includes our 'events' 1-minute rate.
+# We see the output includes our events' 1-minute rate.
 #
 # In the real world, you would emit this to graphite or another metrics store,
 # like so:
@@ -115,12 +118,12 @@ class LogStash::Filters::Metrics < LogStash::Filters::Base
   # syntax: `timer => [ "name of metric", "%{time_value}" ]`
   config :timer, :validate => :hash, :default => {}
 
-  # Don't track events that have @timestamp older than some number of seconds.
+  # Don't track events that have `@timestamp` older than some number of seconds.
   #
   # This is useful if you want to only include events that are near real-time
   # in your metrics.
   #
-  # Example, to only count events that are within 10 seconds of real-time, you
+  # For example, to only count events that are within 10 seconds of real-time, you
   # would do this:
   #
   #     filter {
@@ -144,7 +147,7 @@ class LogStash::Filters::Metrics < LogStash::Filters::Base
   # Possible values are 1, 5, and 15.
   config :rates, :validate => :array, :default => [1, 5, 15]
 
-  # The percentiles that should be measured
+  # The percentiles that should be measured and emitted for timer values.
   config :percentiles, :validate => :array, :default => [1, 5, 10, 90, 95, 99, 100]
 
   def register

data/logstash-filter-metrics.gemspec

@@ -1,7 +1,7 @@
 Gem::Specification.new do |s|
 
   s.name            = 'logstash-filter-metrics'
-  s.version         = '4.0.1'
+  s.version         = '4.0.2'
   s.licenses        = ['Apache License (2.0)']
   s.summary         = "The metrics filter is useful for aggregating metrics."
   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"
@@ -20,7 +20,7 @@ Gem::Specification.new do |s|
   s.metadata = { "logstash_plugin" => "true", "logstash_group" => "filter" }
 
   # Gem dependencies
-  s.add_runtime_dependency "logstash-core-plugin-api", "~> 2.0"
+  s.add_runtime_dependency "logstash-core-plugin-api", ">= 1.60", "<= 2.99"
   s.add_runtime_dependency "metriks"                          #(MIT license)
   s.add_runtime_dependency "thread_safe"
 

metadata

@@ -1,29 +1,35 @@
 --- !ruby/object:Gem::Specification
 name: logstash-filter-metrics
 version: !ruby/object:Gem::Version
-  version: 4.0.1
+  version: 4.0.2
 platform: ruby
 authors:
 - Elastic
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2016-05-09 00:00:00.000000000 Z
+date: 2016-07-14 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '1.60'
+    - - "<="
       - !ruby/object:Gem::Version
-        version: '2.0'
+        version: '2.99'
   name: logstash-core-plugin-api
   prerelease: false
   type: :runtime
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '1.60'
+    - - "<="
       - !ruby/object:Gem::Version
-        version: '2.0'
+        version: '2.99'
 - !ruby/object:Gem::Dependency
   requirement: !ruby/object:Gem::Requirement
     requirements:
@@ -103,7 +109,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project:
-rubygems_version: 2.4.8
+rubygems_version: 2.6.3
 signing_key:
 specification_version: 4
 summary: The metrics filter is useful for aggregating metrics.