logspout
logspout copied to clipboard
gliderlabs
Add redis route target
This is a rebase of https://github.com/progrium/logspout/pull/24. Streams output to redis, appending to a list named after the container. Ideas for improvement or future features:
- option to append all logs to a specific key?
- using pub/sub instead of a list
So based on the previous PR on this, it seems like there is demand. But it would be good to do it in a way that is most common. Can I get some feedback from others that want Redis on whether this is a good approach?
Redis Lists and Channels are most common. A perfect solution would support both options (configurable), but starting with lists is fine for now as well. e.g. logstash redis input
This is a great opportunity to try the module system in master that will let you build logspout against a custom redis adapter package living in a separate repository.
Actually, now that I've seen that Redis is basically the most popular way to make logstash HA, I'd take this as a first-class adapter.
Great; I see there's been a bit of refactoring so I'll update my branch for this PR accordingly soon.
I have created an adapter for sending events to Redis in Logstash json layout. Feedback on https://github.com/rtoma/logspout-redis-logstash is much appreciated, since it my first Golang project.
