Metriccatcher output plugin v3.0.2

• Plugin version: v3.0.2
• Released on: 2017-08-16
• Changelog

For other versions, see the overview list.

To learn more about Logstash, see the Logstash Reference.

For 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.

This 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"
        }
}

This plugin supports the following configuration options plus the Common options described later.

Also see Common options for a list of options supported by all output plugins.

• 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)

• 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)

• 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)

• Value type is string
• Default value is "localhost"

The address of the MetricCatcher

• 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)

• Value type is number
• Default value is 1420

The port to connect on your MetricCatcher

• 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)

• 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)

These configuration options are supported by all output plugins:

• 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.

• 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.

• 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"
  }
}