Docs
Logstash Reference [5.1] » Input plugins » redis
«  rackspace     relp  »

redisedit

  • Version: 3.1.1
  • Released on: 2016-07-14
  • Changelog
  • Compatible: 5.1.2, 5.1.1, 5.0.0, 2.4.1, 2.4.0

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+, and the 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 performance and 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 or newer. Anything older does not support the operations used by batching.

 

Synopsisedit

This plugin supports the following configuration options:

Required configuration options:

redis {
    data_type => ...
    key => ...
}

Available configuration options:

Setting Input typeRequiredDefault value

add_field

hash

No

{}

batch_count

number

No

125

codec

codec

No

"plain"

data_type

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

Yes

db

number

No

0

enable_metric

boolean

No

true

host

string

No

"127.0.0.1"

id

string

No

key

string

Yes

password

password

No

port

number

No

6379

tags

array

No

threads

number

No

1

timeout

number

No

5

type

string

No

Detailsedit

 

add_fieldedit

  • Value type is hash
  • Default value is {}

Add a field to an event

batch_countedit

  • Value type is number
  • Default value is 125

The number of events to return from Redis using EVAL.

codecedit

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

data_typeedit

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

  • Value type is number
  • Default value is 0

The Redis database number.

enable_metricedit

  • Value type is boolean
  • Default value is true

Disable or enable metric collection and reporting for this specific plugin instance. By default we record metrics from all plugins, but you can disable metrics collection for a specific plugin.

hostedit

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

The hostname of your Redis server.

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

Add a unique named ID to the plugin instance. This ID is used for tracking information for a specific configuration of the plugin and will be useful for debugging purposes.

output {
 stdout {
   id => "debug_stdout"
 }
}

If you don’t explicitly set this field, Logstash will generate a unique name.

keyedit

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

passwordedit

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

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

portedit

  • Value type is number
  • Default value is 6379

The port to connect on.

tagsedit

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

threadsedit

  • Value type is number
  • Default value is 1

timeoutedit

  • Value type is number
  • Default value is 5

Initial connection timeout in seconds.

typeedit

  • 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 can also use the type to search for it in Kibana.

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

«  rackspace     relp  »