CentOS centralised logging, syslogd, rsyslog, syslog-ng, logstash sender?
Posted
by
benbradley
on Server Fault
See other posts from Server Fault
or by benbradley
Published on 2012-11-28T16:14:20Z
Indexed on
2012/11/28
17:06 UTC
Read the original article
Hit count: 349
I'm trying to figure out the best way to setup a central place to store and interrogate server logs. syslog, Apache, MySQL etc.
I've found a few different options but I'm not sure what would be best. I'm looking for something that is easy to install and keep updated on many virtual machines. I can add it to a VM template going forward but I'd also like it to be easy to install to keep the VM complexity down.
The options I've found so far are:
- syslogd
- syslog-ng
- rsyslog
- syslogd/syslog-ng/rsyslog to logstash/ElasticSearch
- logstash agent in each log "client" to send to Redis/logstash/ElasticSearch
And all sorts of permutations of the above.
What's the most resilient and light from the log "client" perspective?
I'd like to avoid the situation where log "clients" hang because they are unable to send their logs to the logging server.
Also I would still like to keep local logging and the rotation/retention provided by logrotate in place.
Any ideas/suggestions or reasons for or against any of the above?
Or suggestions of a different structure entirely?
Cheers, B
© Server Fault or respective owner