Metriccatcher output plugin
editMetriccatcher output plugin
edit- Plugin version: v3.0.4
- Released on: 2018-04-06
- Changelog
Installation
editFor plugins not bundled by default, it is easy to install by running bin/logstash-plugin install logstash-output-metriccatcher
. See Working with plugins for more details.
Getting Help
editFor questions about the plugin, open a topic in the Discuss forums. For bugs or feature requests, open an issue in Github. For the list of Elastic supported plugins, please consult the Elastic Support Matrix.
Description
editThis output ships metrics to MetricCatcher, allowing you to utilize Coda Hale’s Metrics.
More info on MetricCatcher: https://github.com/clearspring/MetricCatcher
At Clearspring, we use it to count the response codes from Apache logs:
metriccatcher { host => "localhost" port => "1420" type => "apache-access" fields => [ "response" ] meter => { "%{host}.apache.response.%{response}" => "1" } }
Metriccatcher Output Configuration Options
editThis plugin supports the following configuration options plus the Common Options described later.
Setting | Input type | Required |
---|---|---|
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
Also see Common Options for a list of options supported by all output plugins.
biased
edit- Value type is hash
- There is no default value for this setting.
The metrics to send. This supports dynamic strings like %{host}
for metric names and also for values. This is a hash field with key
of the metric name, value of the metric value.
The value will be coerced to a floating point value. Values which cannot be coerced will zero (0)
counter
edit- Value type is hash
- There is no default value for this setting.
The metrics to send. This supports dynamic strings like %{host}
for metric names and also for values. This is a hash field with key
of the metric name, value of the metric value. Example:
counter => { "%{host}.apache.hits.%{response} => "1" }
The value will be coerced to a floating point value. Values which cannot be coerced will zero (0)
gauge
edit- Value type is hash
- There is no default value for this setting.
The metrics to send. This supports dynamic strings like %{host}
for metric names and also for values. This is a hash field with key
of the metric name, value of the metric value.
The value will be coerced to a floating point value. Values which cannot be coerced will zero (0)
meter
edit- Value type is hash
- There is no default value for this setting.
The metrics to send. This supports dynamic strings like %{host}
for metric names and also for values. This is a hash field with key
of the metric name, value of the metric value.
The value will be coerced to a floating point value. Values which cannot be coerced will zero (0)
timer
edit- Value type is hash
- There is no default value for this setting.
The metrics to send. This supports dynamic strings like %{host} for metric names and also for values. This is a hash field with key of the metric name, value of the metric value. Example:
timer => { "%{host}.apache.response_time => "%{response_time}" }
The value will be coerced to a floating point value. Values which cannot be coerced will zero (0)
uniform
edit- Value type is hash
- There is no default value for this setting.
The metrics to send. This supports dynamic strings like %{host}
for metric names and also for values. This is a hash field with key
of the metric name, value of the metric value.
The value will be coerced to a floating point value. Values which cannot be coerced will zero (0)
Common Options
editThe following configuration options are supported by all output plugins:
codec
edit- Value type is codec
-
Default value is
"plain"
The codec used for output data. Output codecs are a convenient method for encoding your data before it leaves the output, without needing a separate filter in your Logstash pipeline.
enable_metric
edit- Value type is boolean
-
Default value is
true
Disable or enable metric logging for this specific plugin instance by default we record all the metrics we can, but you can disable metrics collection for a specific plugin.
id
edit- Value type is string
- There is no default value for this setting.
Add a unique ID
to the plugin configuration. If no ID is specified, Logstash will generate one.
It is strongly recommended to set this ID in your configuration. This is particularly useful
when you have two or more plugins of the same type, for example, if you have 2 metriccatcher outputs.
Adding a named ID in this case will help in monitoring Logstash when using the monitoring APIs.
output { metriccatcher { id => "my_plugin_id" } }