logstash-filter-metrics 4.0.1 → 4.0.2
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +3 -0
- data/lib/logstash/filters/metrics.rb +18 -15
- data/logstash-filter-metrics.gemspec +2 -2
- metadata +13 -7
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 57bfe0e3b3d5fdd1ea24b7bad5576e6d1689e661
|
4
|
+
data.tar.gz: b2c9a453d532be098be076b6a3af4b1d8961645a
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 1e7521606f0700ae3c18af48c833f7eee82671ba9a4cdcebb2026eb38a74a106167350c64712bae09329783e64e042492eca94d351048d2e828c6374b6cb458e
|
7
|
+
data.tar.gz: 8ed0fdea1046750ca4c515f5ce5e28e765e5f8a35cc0d8854af697a61294f3fb36b9d5ee89ac58a37504fbcd2b421241918fd15deecb0b3edecec4c428548f5f
|
data/CHANGELOG.md
CHANGED
@@ -10,7 +10,7 @@ require "logstash/namespace"
|
|
10
10
|
# dotted notation to avoid colliding with versions of Elasticsearch 2.0+. Please
|
11
11
|
# note the changes in the documentation (underscores and sub-fields used).
|
12
12
|
#
|
13
|
-
# For example, if you have a field
|
13
|
+
# For example, if you have a field `response` that is
|
14
14
|
# a http response code, and you want to count each
|
15
15
|
# kind of response, you can do this:
|
16
16
|
# [source,ruby]
|
@@ -22,7 +22,7 @@ require "logstash/namespace"
|
|
22
22
|
# }
|
23
23
|
#
|
24
24
|
# Metrics are flushed every 5 seconds by default or according to
|
25
|
-
#
|
25
|
+
# `flush_interval`. Metrics appear as
|
26
26
|
# new events in the event stream and go through any filters
|
27
27
|
# that occur after as well as outputs.
|
28
28
|
#
|
@@ -32,30 +32,33 @@ require "logstash/namespace"
|
|
32
32
|
# The event that is flushed will include every 'meter' and 'timer'
|
33
33
|
# metric in the following way:
|
34
34
|
#
|
35
|
-
#
|
35
|
+
# ==== `meter` values
|
36
36
|
#
|
37
37
|
# For a `meter => "something"` you will receive the following fields:
|
38
38
|
#
|
39
39
|
# * "[thing][count]" - the total count of events
|
40
|
-
# * "[thing][rate_1m]" - the 1-minute
|
41
|
-
# * "[thing][rate_5m]" - the 5-minute
|
42
|
-
# * "[thing][rate_15m]" - the 15-minute
|
40
|
+
# * "[thing][rate_1m]" - the per-second event rate in a 1-minute sliding window
|
41
|
+
# * "[thing][rate_5m]" - the per-second event rate in a 5-minute sliding window
|
42
|
+
# * "[thing][rate_15m]" - the per-second event rate in a 15-minute sliding window
|
43
43
|
#
|
44
|
-
#
|
44
|
+
# ==== `timer` values
|
45
45
|
#
|
46
46
|
# For a `timer => [ "thing", "%{duration}" ]` you will receive the following fields:
|
47
47
|
#
|
48
48
|
# * "[thing][count]" - the total count of events
|
49
|
-
# * "[thing][rate_1m]" - the
|
50
|
-
# * "[thing][rate_5m]" - the
|
51
|
-
# * "[thing][rate_15m]" - the
|
49
|
+
# * "[thing][rate_1m]" - the per-second event rate in a 1-minute sliding window
|
50
|
+
# * "[thing][rate_5m]" - the per-second event rate in a 5-minute sliding window
|
51
|
+
# * "[thing][rate_15m]" - the per-second event rate in a 15-minute sliding window
|
52
52
|
# * "[thing][min]" - the minimum value seen for this metric
|
53
53
|
# * "[thing][max]" - the maximum value seen for this metric
|
54
54
|
# * "[thing][stddev]" - the standard deviation for this metric
|
55
55
|
# * "[thing][mean]" - the mean for this metric
|
56
56
|
# * "[thing][pXX]" - the XXth percentile for this metric (see `percentiles`)
|
57
57
|
#
|
58
|
-
#
|
58
|
+
# The default lengths of the event rate window (1, 5, and 15 minutes)
|
59
|
+
# can be configured with the `rates` option.
|
60
|
+
#
|
61
|
+
# ==== Example: Computing event rate
|
59
62
|
#
|
60
63
|
# For a simple example, let's track how many events per second are running
|
61
64
|
# through logstash:
|
@@ -96,7 +99,7 @@ require "logstash/namespace"
|
|
96
99
|
# rate: 25875.892745934525
|
97
100
|
# rate: 26836.42375967113
|
98
101
|
#
|
99
|
-
# We see the output includes our
|
102
|
+
# We see the output includes our events' 1-minute rate.
|
100
103
|
#
|
101
104
|
# In the real world, you would emit this to graphite or another metrics store,
|
102
105
|
# like so:
|
@@ -115,12 +118,12 @@ class LogStash::Filters::Metrics < LogStash::Filters::Base
|
|
115
118
|
# syntax: `timer => [ "name of metric", "%{time_value}" ]`
|
116
119
|
config :timer, :validate => :hash, :default => {}
|
117
120
|
|
118
|
-
# Don't track events that have
|
121
|
+
# Don't track events that have `@timestamp` older than some number of seconds.
|
119
122
|
#
|
120
123
|
# This is useful if you want to only include events that are near real-time
|
121
124
|
# in your metrics.
|
122
125
|
#
|
123
|
-
#
|
126
|
+
# For example, to only count events that are within 10 seconds of real-time, you
|
124
127
|
# would do this:
|
125
128
|
#
|
126
129
|
# filter {
|
@@ -144,7 +147,7 @@ class LogStash::Filters::Metrics < LogStash::Filters::Base
|
|
144
147
|
# Possible values are 1, 5, and 15.
|
145
148
|
config :rates, :validate => :array, :default => [1, 5, 15]
|
146
149
|
|
147
|
-
# The percentiles that should be measured
|
150
|
+
# The percentiles that should be measured and emitted for timer values.
|
148
151
|
config :percentiles, :validate => :array, :default => [1, 5, 10, 90, 95, 99, 100]
|
149
152
|
|
150
153
|
def register
|
@@ -1,7 +1,7 @@
|
|
1
1
|
Gem::Specification.new do |s|
|
2
2
|
|
3
3
|
s.name = 'logstash-filter-metrics'
|
4
|
-
s.version = '4.0.
|
4
|
+
s.version = '4.0.2'
|
5
5
|
s.licenses = ['Apache License (2.0)']
|
6
6
|
s.summary = "The metrics filter is useful for aggregating metrics."
|
7
7
|
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|
|
|
20
20
|
s.metadata = { "logstash_plugin" => "true", "logstash_group" => "filter" }
|
21
21
|
|
22
22
|
# Gem dependencies
|
23
|
-
s.add_runtime_dependency "logstash-core-plugin-api", "
|
23
|
+
s.add_runtime_dependency "logstash-core-plugin-api", ">= 1.60", "<= 2.99"
|
24
24
|
s.add_runtime_dependency "metriks" #(MIT license)
|
25
25
|
s.add_runtime_dependency "thread_safe"
|
26
26
|
|
metadata
CHANGED
@@ -1,29 +1,35 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: logstash-filter-metrics
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 4.0.
|
4
|
+
version: 4.0.2
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Elastic
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2016-
|
11
|
+
date: 2016-07-14 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
requirement: !ruby/object:Gem::Requirement
|
15
15
|
requirements:
|
16
|
-
- - "
|
16
|
+
- - ">="
|
17
|
+
- !ruby/object:Gem::Version
|
18
|
+
version: '1.60'
|
19
|
+
- - "<="
|
17
20
|
- !ruby/object:Gem::Version
|
18
|
-
version: '2.
|
21
|
+
version: '2.99'
|
19
22
|
name: logstash-core-plugin-api
|
20
23
|
prerelease: false
|
21
24
|
type: :runtime
|
22
25
|
version_requirements: !ruby/object:Gem::Requirement
|
23
26
|
requirements:
|
24
|
-
- - "
|
27
|
+
- - ">="
|
28
|
+
- !ruby/object:Gem::Version
|
29
|
+
version: '1.60'
|
30
|
+
- - "<="
|
25
31
|
- !ruby/object:Gem::Version
|
26
|
-
version: '2.
|
32
|
+
version: '2.99'
|
27
33
|
- !ruby/object:Gem::Dependency
|
28
34
|
requirement: !ruby/object:Gem::Requirement
|
29
35
|
requirements:
|
@@ -103,7 +109,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
103
109
|
version: '0'
|
104
110
|
requirements: []
|
105
111
|
rubyforge_project:
|
106
|
-
rubygems_version: 2.
|
112
|
+
rubygems_version: 2.6.3
|
107
113
|
signing_key:
|
108
114
|
specification_version: 4
|
109
115
|
summary: The metrics filter is useful for aggregating metrics.
|