Influxdb output pluginedit

  • Plugin version: v5.0.1
  • 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.

Descriptionedit

This output lets you output Metrics to InfluxDB (>= 0.9.0-rc31)

The configuration here attempts to be as friendly as possible and minimize the need for multiple definitions to write to multiple measurements and still be efficient

the InfluxDB API let’s you do some semblance of bulk operation per http call but each call is database-specific

You can learn more at InfluxDB homepage

Influxdb Output Configuration Optionsedit

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.

 

allow_time_overrideedit

  • Value type is boolean
  • Default value is false

Allow the override of the time column in the event?

By default any column with a name of time will be ignored and the time will be determined by the value of @timestamp.

Setting this to true allows you to explicitly set the time column yourself

Note: time must be an epoch value in either seconds, milliseconds or microseconds

coerce_valuesedit

  • Value type is hash
  • Default value is {}

Allow value coercion

this will attempt to convert data point values to the appropriate type before posting otherwise sprintf-filtered numeric values could get sent as strings format is {'column_name' => 'datatype'}

currently supported datatypes are integer and float

data_pointsedit

  • This is a required setting.
  • Value type is hash
  • Default value is {}

Hash of key/value pairs representing data points to send to the named database Example: {'column1' => 'value1', 'column2' => 'value2'}

Events for the same measurement will be batched together where possible Both keys and values support sprintf formatting

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

The database to write - supports sprintf formatting

exclude_fieldsedit

  • Value type is array
  • Default value is ["@timestamp", "@version", "sequence", "message", "type"]

An array containing the names of fields from the event to exclude from the data points

Events, in general, contain keys "@version" and "@timestamp". Other plugins may add others that you’ll want to exclude (such as "command" from the exec plugin).

This only applies when use_event_fields_for_data_points is true.

flush_sizeedit

  • Value type is number
  • Default value is 100

This setting controls how many events will be buffered before sending a batch of events. Note that these are only batched for the same measurement

hostedit

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

The hostname or IP address to reach your InfluxDB instance

idle_flush_timeedit

  • Value type is number
  • Default value is 1

The amount of time since last flush before a flush is forced.

This setting helps ensure slow event rates don’t get stuck in Logstash. For example, if your flush_size is 100, and you have received 10 events, and it has been more than idle_flush_time seconds since the last flush, logstash will flush those 10 events automatically.

This helps keep both fast and slow log streams moving along in near-real-time.

initial_delayedit

  • Value type is number
  • Default value is 1

The amount of time in seconds to delay the initial retry on connection failure.

The delay will increase exponentially for each retry attempt (up to max_retries).

max_retriesedit

  • Value type is number
  • Default value is 3

The number of time to retry recoverable errors before dropping the events.

A value of -1 will cause the plugin to retry indefinately. A value of 0 will cause the plugin to never retry. Otherwise it will retry up to the specified mumber of times.

measurementedit

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

Measurement name - supports sprintf formatting

passwordedit

  • Value type is password
  • Default value is nil

The password for the user who access to the named database

portedit

  • Value type is number
  • Default value is 8086

The port for InfluxDB

retention_policyedit

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

The retention policy to use

send_as_tagsedit

  • Value type is array
  • Default value is ["host"]

An array containing the names of fields to send to Influxdb as tags instead of fields. Influxdb 0.9 convention is that values that do not change every request should be considered metadata and given as tags.

ssledit

  • Value type is boolean
  • Default value is false

Enable SSL/TLS secured communication to InfluxDB

time_precisionedit

  • Value can be any of: n, u, ms, s, m, h
  • Default value is "ms"

Set the level of precision of time

only useful when overriding the time value

use_event_fields_for_data_pointsedit

  • Value type is boolean
  • Default value is false

Automatically use fields from the event as the data points sent to Influxdb

useredit

  • Value type is string
  • Default value is nil

The user who has access to the named database

Common Optionsedit

The following configuration options are supported by all output plugins:

Setting Input typeRequired

codec

codec

No

enable_metric

boolean

No

id

string

No

workers

number

No

codecedit

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

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

workersedit

  • Value type is string
  • Default value is 1