remote_syslog2

remote_syslog2 copied to clipboard

This is an issue we face managing a small cluster of servers that have papertrail. Our yml file is stored in a git repo that is auto-updated every minute. If we have to add a new log path to our shared yml file, we push it to the repo and it updates on all servers.

However, remote_syslog doesn't automatically update new log-paths from this file - unless we restart the instance on all servers, manually.

remote_syslog should periodically reload the log paths from the .yml file (for old and new entries) and check if these files exist now. Alternatively, the papertrail server can store config files for individual/groups of systems. The daemon polls the server periodically and gets an updated list.

I think a centralised web UI is a much better way to manage log-paths and other config.. It does make things more complex, and bring the idea of security in. But these are just ideas to solve the problem of configuring & managing papertrail easily on small (and large) clusters.

If using something like Chef, when the YAML gets updated, the service is triggered to restart.