filebeat能夠把收集到的日誌傳輸到redis集羣中,可是logstash如何從從redis集羣中拉取數據的呢?
ogstash使用的是7.3版本html
通過查看官網文檔,發現logstash7.3版本不支持從redis集羣中拉取數據git
host參數的值是string,不支持列表github
For other versions, see the Versioned plugin docs.redis
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.json
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.ide
For more information about Redis, see http://redis.io/ui
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.this
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 all input plugins.code
batch_count
edit125
The number of events to return from Redis using EVAL.
data_type
editlist
, channel
, pattern_channel
Specify either list or channel. If data_type
is list
, then we will BLPOP the key. If data_type
is channel
, then we will SUBSCRIBE to the key. If data_type
is pattern_channel
, then we will PSUBSCRIBE to the key.
db
edit0
The Redis database number.
host
edit"127.0.0.1"
The hostname of your Redis server.
key
editThe name of a Redis list or channel.
password
editPassword to authenticate with. There is no authentication by default.
port
edit6379
The port to connect on.
ssl
editfalse
Enable SSL support.
threads
edit1
timeout
edit5
Initial connection timeout in seconds.
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 |
add_field
edit{}
Add a field to an event
codec
edit"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
edittrue
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.
id
editAdd 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 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
editAdd any number of arbitrary tags to your event.
This can help with processing later.
type
editAdd 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.