Class: LogStash::Filters::Metrics
- Inherits:
-
Base
- Object
- Base
- LogStash::Filters::Metrics
- Defined in:
- lib/logstash/filters/metrics.rb
Overview
The metrics filter is useful for aggregating metrics.
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
-
filter
metrics { meter => [ "http.%{response" ] add_tag => "metric" }}
Metrics are flushed every 5 seconds by default or according to ‘flush_interval’. Metrics appear as new events in the event stream and go through any filters that occur after as well as outputs.
In general, you will want to add a tag to your metrics and have an output explicitly look for that tag.
The event that is flushed will include every ‘meter’ and ‘timer’ metric in the following way:
#### ‘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)
#### ‘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.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
For a simple example, let’s track how many events per second are running through logstash:
- source,ruby
-
input {
generator { type => "generated" }}
filter {
if [type] == "generated" { metrics { meter => "events" add_tag => "metric" } }}
output {
# only emit events with the 'metric' tag if "metric" in [] { stdout { codec => line { format => "rate: %{events.rate_1m}" } } }}
Running the above:
- source,ruby
-
% bin/logstash -f example.conf rate: 23721.983566819246 rate: 24811.395722536377 rate: 25875.892745934525 rate: 26836.42375967113
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:
- source,ruby
-
output {
graphite { metrics => [ "events.rate_1m", "%{events.rate_1m}" ] }}
Instance Method Summary collapse
-
#filter(event) ⇒ Object
def register.
-
#flush(options = {}) ⇒ Object
def filter.
- #register ⇒ Object
Instance Method Details
#filter(event) ⇒ Object
def register
159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 |
# File 'lib/logstash/filters/metrics.rb', line 159 def filter(event) return unless filter?(event) # TODO(piavlo): This should probably be moved to base filter class. if @ignore_older_than > 0 && Time.now - event..time > @ignore_older_than @logger.debug("Skipping metriks for old event", :event => event) return end @meter.each do |m| @metric_meters[event.sprintf(m)].mark end @timer.each do |name, value| @metric_timers[event.sprintf(name)].update(event.sprintf(value).to_f) end end |
#flush(options = {}) ⇒ Object
def filter
177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 |
# File 'lib/logstash/filters/metrics.rb', line 177 def flush( = {}) # Add 5 seconds to @last_flush and @last_clear counters # since this method is called every 5 seconds. @last_flush.update { |v| v + 5 } @last_clear.update { |v| v + 5 } # Do nothing if there's nothing to do ;) return unless should_flush? event = LogStash::Event.new event["message"] = Socket.gethostname @metric_meters.each_pair do |name, metric| flush_rates event, name, metric metric.clear if should_clear? end @metric_timers.each_pair do |name, metric| flush_rates event, name, metric # These 4 values are not sliding, so they probably are not useful. event["#{name}.min"] = metric.min event["#{name}.max"] = metric.max # timer's stddev currently returns variance, fix it. event["#{name}.stddev"] = metric.stddev ** 0.5 event["#{name}.mean"] = metric.mean @percentiles.each do |percentile| event["#{name}.p#{percentile}"] = metric.snapshot.value(percentile / 100.0) end metric.clear if should_clear? end # Reset counter since metrics were flushed @last_flush.value = 0 if should_clear? #Reset counter since metrics were cleared @last_clear.value = 0 @metric_meters.clear @metric_timers.clear end filter_matched(event) return [event] end |
#register ⇒ Object
144 145 146 147 148 149 150 151 152 153 154 155 156 157 |
# File 'lib/logstash/filters/metrics.rb', line 144 def register require "metriks" require "socket" require "atomic" require "thread_safe" @last_flush = Atomic.new(0) # how many seconds ago the metrics where flushed. @last_clear = Atomic.new(0) # how many seconds ago the metrics where cleared. @random_key_preffix = SecureRandom.hex unless (@rates - [1, 5, 15]).empty? raise LogStash::ConfigurationError, "Invalid rates configuration. possible rates are 1, 5, 15. Rates: #{rates}." end @metric_meters = ThreadSafe::Cache.new { |h,k| h[k] = Metriks.meter metric_key(k) } @metric_timers = ThreadSafe::Cache.new { |h,k| h[k] = Metriks.timer metric_key(k) } end |