It'd be nice for taskd to use a custom log output which includes some task details (id, task name) in the log line. That'd make it easier to find specific stuff in the log file.
If we do [#5328], then we could just change the logging config in the INI file to include %(processName)s to cover this.
%(processName)s
Tickets: #5328
forge:tv/5721
After checking out the branch, apply the following one-line change to production.ini:
production.ini
(env-allura)root@h6v6034:/var/local/allura/Allura(tv/5721)$ diff -u production.ini production.ini.new --- production.ini 2013-06-05 23:25:23.000000000 +0000 +++ production.ini.new 2013-06-05 23:25:00.000000000 +0000 @@ -358,7 +358,7 @@ # If you create additional handlers, add them as a key to [handlers] [handler_console] -class = handlers.WatchedFileHandler +class = allura.lib.utils.CustomWatchedFileHandler args = ('/var/log/allura/allura.log', 'a') # make this be a logfile that is writable by the process level = NOTSET formatter = generic
Restart taskd and tail -f /var/log/allura/allura.log. Do stuff in the web app, e.g. create a project, create a ticket, post a comment.
tail -f /var/log/allura/allura.log
Log in to post a comment.
If we do [#5328], then we could just change the logging config in the INI file to include
%(processName)sto cover this.Related
Tickets:
#5328forge:tv/5721
After checking out the branch, apply the following one-line change to
production.ini:Restart taskd and
tail -f /var/log/allura/allura.log. Do stuff in the web app, e.g. create a project, create a ticket, post a comment.