Filebeat redis output doesn't support redis cluster mode

Elastic Stack Beats
1

I am using filebeat 5.4.0 with redis output and I noticed filebeat doesn't support access to redis cluster configuration endpoint. I am using AWS redis cluster mode on (engine 3.2.4) and filebeat is not able to handle MOVED events (https://redis.io/docs/reference/cluster-spec/).

This is the error I get from filebeat logs:

2017-07-14T02:35:51Z ERR Failed to RPUSH event to list with MOVED 6715 x.x.x.x:6379

and here my filebeat.yml output.redis section:

output.redis:
hosts: ["xxxx.xxxx.clustercfg.usw2.cache.amazonaws.com:6379"]
datatype: "list"
key: "filebeat:%{[environment]}"

As per my understanding, filebeat should be aware of this and implement corresponding logic to redirect PUSH to node returned by MOVED (redis-cli, for instance do it).

Note: logstash should act in the same way.

2 Likes
2

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.