Opentsdb output pluginedit

  • Plugin version: v3.1.2
  • Released on: 2017-06-23
  • Changelog

Getting Helpedit

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 allows you to pull metrics from your logs and ship them to opentsdb. Opentsdb is an open source tool for storing and graphing metrics.

Opentsdb Output Configuration Optionsedit

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

SettingInput typeRequired










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



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

The address of the opentsdb server.


  • This is a required setting.
  • Value type is array
  • There is no default value for this setting.

The metric(s) to use. This supports dynamic strings like %{source_host} for metric names and also for values. This is an array field with key of the metric name, value of the metric value, and multiple tag,values . Example:

      %{uptime_1m} " ,
      "hostname" ,
      "anotherhostname" ,

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 4242

The port to connect on your graphite server.

Common Optionsedit

The following 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 grok filters. Adding a named ID in this case will help in monitoring Logstash when using the monitoring APIs.

output {
 stdout {
   id => "my_plugin_id"


  • Value type is string
  • Default value is 1