On 20 March 2015 at 21:25, Simon Hill simonhill...@gmail.com wrote:
I'm trying to use https://github.com/gliderlabs/logspout to siphon remote
prosody docker logs to Paper Trail. I have the config
*console; -- Log to the console, useful for debugging with daemonize=false
For some unknown
Thanks Matt. It turned out that it had nothing to do with prosody. Logs are
capturing fine now.I had a misconfigured log capture filter meant to filter
out weave traffic that was also knocking out anything with 'debug' in it.
oops.
On Sat, Mar 21, 2015 at 5:36 AM, Matthew Wild mwi...@gmail.com
I'm trying to use https://github.com/gliderlabs/logspout to siphon remote
prosody docker logs to Paper Trai https://papertrailapp.coml. I have the
config
*console; -- Log to the console, useful for debugging with daemonize=false
For some unknown reason, logspout doesn't pick this up. I have
