Fluentd output plugin to upload/publish event data to Redis storage.

Forked from redis-store which forked from redisstore plugin I'm using this in high traffic production environment

Currently the plugin supports following Redis commands:

• set by string type (of the plugin)
• lpush/rpush by list type
• sadd by set type
• zadd by zset type
• publish by publish type

• plain(as is)
• JSON
• MessagePack

Redis commands require key and value.
For key, the plugin supports either way;

1. Specify a fixed key.
   You can do this simply using key option in td-agent configuration file.

   type redis_store
   key userdata

2. Lookup a key string in every event data by a lookup path.
   If event data have structured data like

   { "user": { "name": "Kei" } }

   and you want to use each name of user, you can use key_path option.

   type redis_store
   key_path user.name

   With the above data, Kei will be a key.

In addition, key_prefix and key_suffix are useful in some cases. Both are available either key and key_path

type redis_store
key_path user.name
key_prefix ouruser.
key_suffix .accesslog

With the previous data, key will be outuser.Kei.accesslog.

To determine what value in every event data to be srtored, you have two options;

1. Store extracted data in event data, by a lookup path with value_path option.
   It works like key_path.
2. Store whole data.
   This is default behavior. To do it, simply omit value_path option.

/usr/lib64/fluent/ruby/bin/fluent-gem install fluent-plugin-redis-store

No more options than common options.

If value_expire is set, the plugin assumes that the score in the SortedSet is based on timestamp and it deletes expired members every after new event data arrives.

No more options than common options.

Copyright (c) 2013 moaikids
Copyright (c) 2014 HANAI Tohru
Copyright (c) 2016 Gian Giovani

Apache License, Version 2.0