5 ms·

Is there a reason you're writing another daemon? Have you seen http://fluentd.org/ http://fluentd.org/ which seems to already have packages for many OSes as wel

• snewman 14y ago
  Good question (and thanks for the fluentd pointer). The answer boils down to: 1. We want to provide a number of functions (e.g. tailing logs, gathering system metrics, reading from application-specific monitoring interfaces). There are packages such as fluentd and logstash that provide this type of functionality, but not all in one place. 2. As a multi-tenant SaaS offering, we have some extra requirements around authentication and security. 3. We want to absolutely minimize the effort needed to install the daemon. Ideally, for most users, the steps would be "download archive, extract archive, invoke setup script". The more dependencies (e.g. Ruby) we incur, the harder it is to keep installation clean and reliable across distros. 4. We also want to make management (starting, stopping, troubleshooting) as simple as possible. This calls for minimizing layers that might add their own log output or separate log files, separate processes, etc. So, while we might borrow ideas or even (license permitting) code from existing projects, we expect to have to do some reworking. In any case, the platform question applies even if we re-use an existing daemon -- we don't want to use one that's based on a platform that might cause installation problems.
  • skram 14y ago
    Fair enough and good luck in the space!