-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
The current logstash redis plugin works nicely, but does not allow me to specify a redis db to be used (which I think makes it default to 0).
We currently maintain a separate redis instance for Jenkins, but it would be great to be able to use our (larger, faster, highly available) AWS ElastiCache instead, without the potential of shoving entries into a database already used by a different service.
I had a quick look at the Jedis API docs and they do allow a database number to be specified for a connection. I'm not sure ho to go about adding that functionailty without breaking things, though