Leon Sodhi
Leon Sodhi
``` [root@NAME]# systemctl status remote_syslog remote_syslog.service - remote_syslog2 Loaded: loaded (/etc/systemd/system/remote_syslog.service; enabled; vendor preset: disabled) Active: failed (Result: start-limit) since Mon 2016-05-09 14:15:19 UTC; 5min ago Docs: https://github.com/papertrail/remote_syslog2 Process: 1118...
No idea how to do this, and the first step is figuring out how to reliably repro it.
`--diagnostics` would execute remote_syslog in the foreground, connect, send a message, disconnect, then exit. It should output several log messages so we know what it's doing and that each action...
If I have a directory structure such as: ``` /var/log/test/test.log /var/log/test/subtest ``` and specify `/var/log/test/*` in the config, the following error is produced: ``` 2014-06-06 21:38:46 INFO remote_syslog.go:86 Forwarding /var/log/test/test.log...
This would avoid the situation where something goes wrong and there's no local debug log to look at. The packages could require logrotate as a dependency and provide a rotation...
At the moment, we only see: ``` Starting remote_syslog: ``` and ``` Stopping remote_syslog: ```
Errors such as [this](https://github.com/papertrail/remote_syslog2/blob/39552e6f594d3fa4a74e4581b5945dbe3b8978f6/utils/daemonize.go#L59) don't appear in the debug log.
That would allow us to test new changes on multiple versions of Ruby and avoid situations where a method is called that doesn't exist. For example, [here](https://github.com/papertrail/papertrail-cli/commit/cbbbe1da8edef4c5fc9cb00d49b6965f263ffb1f) `force_encoding` doesn't exist...
`papertrail --min-time '12:30' --max-time '14:30'` will return results after 14:30 today. A workaround is to explicitly specify `today`: `papertrail --min-time '12:30' --max-time 'today 14:30'`
Added a hostname tag that will allow someone to easily override the hostname sent out in the syslog packet. This is particularly useful on services like EC2 where the hostname...