Redis input plugin

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

For other versions, see theVersioned plugin docs.

Getting Help

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.

Description

This input will read events from a Redis instance; it supports both Redis channels and lists.The list command (BLPOP) used by Logstash is supported in Redis v1.3.1+, andthe channel commands used by Logstash are found in Redis v1.3.8+.While you may be able to make these Redis versions work, the best performanceand stability will be found in more recent stable versions. Versions 2.6.0+are recommended.

For more information about Redis, see http://redis.io/

batch_count note: If you use the batch_count setting, you must use a Redis version 2.6.0 ornewer. Anything older does not support the operations used by batching.

Redis Input Configuration Options

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

Setting Input type Required

batch_count

number

No

data_type

string, one of ["list", "channel", "pattern_channel"]

Yes

db

number

No

host

string

No

key

string

Yes

password

password

No

port

number

No

threads

number

No

timeout

number

No

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

 

batch_count

  • Value type is number
  • Default value is 125

The number of events to return from Redis using EVAL.

data_type

  • This is a required setting.
  • Value can be any of: list, channel, pattern_channel
  • There is no default value for this setting.

Specify either list or channel. If redis\_type is list, then we will BLPOP thekey. If redis\_type is channel, then we will SUBSCRIBE to the key.If redis\_type is pattern_channel, then we will PSUBSCRIBE to the key.

db

  • Value type is number
  • Default value is 0

The Redis database number.

host

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

The hostname of your Redis server.

key

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

The name of a Redis list or channel.

password

  • Value type is password
  • There is no default value for this setting.

Password to authenticate with. There is no authentication by default.

port

  • Value type is number
  • Default value is 6379

The port to connect on.

threads

  • Value type is number
  • Default value is 1

timeout

  • Value type is number
  • Default value is 5

Initial connection timeout in seconds.

Common Options

The following configuration options are supported by all input plugins:

Setting Input type Required

add_field

hash

No

codec

codec

No

enable_metric

boolean

No

id

string

No

tags

array

No

type

string

No

Details

 

add_field

  • Value type is hash
  • Default value is {}

Add a field to an event

codec

  • Value type is codec
  • Default value is "plain"

The codec used for input data. Input codecs are a convenient method for decoding your data before it enters the input, without needing a separate filter in your Logstash pipeline.

enable_metric

  • Value type is boolean
  • Default value is true

Disable or enable metric logging for this specific plugin instanceby default we record all the metrics we can, but you can disable metrics collectionfor a specific plugin.

id

  • 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 usefulwhen you have two or more plugins of the same type, for example, if you have 2 redis inputs.Adding a named ID in this case will help in monitoring Logstash when using the monitoring APIs.

input {  redis {    id => "my_plugin_id"  }}

tags

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

Add any number of arbitrary tags to your event.

This can help with processing later.

type

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

Add a type field to all events handled by this input.

Types are used mainly for filter activation.

The type is stored as part of the event itself, so you canalso use the type to search for it in Kibana.

If you try to set a type on an event that already has one (forexample when you send an event from a shipper to an indexer) thena new input will not override the existing type. A type set atthe shipper stays with that event for its life evenwhen sent to another Logstash server.