Redis isn't persistent, see
Redis - Wikipedia details on what it
means in redis terms, but the default behaviour of
redis is not to store anything out of memory.
It's used primarily as an in memory, temporary key/value store that
provides very fast access. Logstash's recommended setup uses redis as a
queuing service between it's various instances, however it used to use an
AMQ system, rabbitmq, which provides actual persistence. I'm not sure why
they swapped though.
If you are taking syslog-ng data and then parsing it into a custom java
app, then Logstash might be a viable alternative as it will save you a
bunch of work.
All that aside, can you clarify what you mean by "I'm wondering about the
role that Redis played in the initial test installation", as that isn't
really explained. Why did you install redis originally?
Regards,
Mark Walkom
Infrastructure Engineer
Campaign Monitor
email: markw@campaignmonitor.com
web: www.campaignmonitor.com
On 30 October 2013 08:03, joergprante@gmail.com joergprante@gmail.comwrote:
Not sure about your requirements. And good answers to Redis are rare on an
ES list. From my understanding, Redis is not really a buffer, it is a
persistent queue, and supports a babylonian plentitude of clients. So if
you want a (central) store with transactional data flow, available for post
processing beside ES, with your devs and sysops loving polyglot
architectures, Redis may be the answer.
If you want just collect and index log messages for yourself, much simpler
setups can be imagined. Solutions like logstash or rsyslog are available.
As you are also like to grow your own apps at home, there is nothing to
prevent you from writing a plugin for ES that starts a syslog daemon, parse
the log messages, and index them
Jörg
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.