Hey guys, I searched Google for: site:http://qos.ch/pipermail/logback-dev/ +redis +appender site:http://qos.ch/pipermail/logback-dev/ +redis ...before messaging. I need some feedback on writing a Redis appender for logback. It is especially useful to do this as an appender instead of putting a program behind the socket appender, because I'll have direct access to the log event, and I'll have a lot of flexibility with regards to saving each field of the event with a suitably descriptive key in Redis. With Redis' fast retrieval and pattern matching support on keys, I'll be able to do fast log analyses using a separate custom tool (which I'm also planning to build and put in the open source domain). Please let me know if I'm going to waste my time, and if the same thing can be achieved with one of the other appenders. Extending DBAppender also didn't make a lot of sense because it's mainly geared towards SQL. Thanks, Juan
Hi Juan, Implementing a redis appender fir logback is probably a very good idea. Shout if you need help. Cheers, On 11/10/2010 9:45 PM, Juan M Uys wrote:
Hey guys,
I searched Google for: site:http://qos.ch/pipermail/logback-dev/ +redis +appender site:http://qos.ch/pipermail/logback-dev/ +redis ...before messaging.
I need some feedback on writing a Redis appender for logback.
It is especially useful to do this as an appender instead of putting a program behind the socket appender, because I'll have direct access to the log event, and I'll have a lot of flexibility with regards to saving each field of the event with a suitably descriptive key in Redis. With Redis' fast retrieval and pattern matching support on keys, I'll be able to do fast log analyses using a separate custom tool (which I'm also planning to build and put in the open source domain).
Please let me know if I'm going to waste my time, and if the same thing can be achieved with one of the other appenders. Extending DBAppender also didn't make a lot of sense because it's mainly geared towards SQL.
Thanks, Juan
Hi Ceki, I don't know if my Github pull request reached you on Saturday night, but basically I have a first draft and it would be great if you can comment: http://github.com/opyate/logback/commit/56cabf8c1ebc7d1fad5caa05c944788d314f... The maintainer of Jedis created an interface for this client, so once he has it in his mainline, I'll be able to stub out some tests. A web-based client is also in the making, modelled after Chainsaw. Thanks, Juan On 12 October 2010 21:27, Ceki Gülcü <ceki@qos.ch> wrote:
Hi Juan,
Implementing a redis appender fir logback is probably a very good idea. Shout if you need help.
Cheers,
On 11/10/2010 9:45 PM, Juan M Uys wrote:
Hey guys,
I searched Google for: site:http://qos.ch/pipermail/logback-dev/ +redis +appender site:http://qos.ch/pipermail/logback-dev/ +redis ...before messaging.
I need some feedback on writing a Redis appender for logback.
It is especially useful to do this as an appender instead of putting a program behind the socket appender, because I'll have direct access to the log event, and I'll have a lot of flexibility with regards to saving each field of the event with a suitably descriptive key in Redis. With Redis' fast retrieval and pattern matching support on keys, I'll be able to do fast log analyses using a separate custom tool (which I'm also planning to build and put in the open source domain).
Please let me know if I'm going to waste my time, and if the same thing can be achieved with one of the other appenders. Extending DBAppender also didn't make a lot of sense because it's mainly geared towards SQL.
Thanks, Juan
_______________________________________________ logback-dev mailing list logback-dev@qos.ch http://qos.ch/mailman/listinfo/logback-dev
participants (2)
-
Ceki Gülcü -
Juan M Uys