#374 Rework Logging Mechanisms
Closed: Fixed None Opened 11 years ago by tflink.

= problem =

The logs for both the blocker tracking app and the sync operation are limited to stdout only instead of being separated out into a file.

= analysis =

The biggest problem here is recording what happens with sync - we used to deal with it by piping the output into a file but with the shift to RPM packaging and hosting in fedora infra, this is no longer an option.

The log messages during normal app use go to httpd's error_log but that isn't as big of a problem.

This bug will serve as a tracker bug for all the functionality which needs to be done in order to properly log output from sync and the blocker tracking app.


It turns out that there is a change going on in infra with regards to their logging perferences. Instead of using a standalone file or stdout, we're supposed to be using syslog so that things get picked up by rsyslog; documentation is available at:

https://fedoraproject.org/wiki/Infrastructure/AppBestPractices#Centralized_logging

Since we're not done with the logging yet and there are still a few things not working, we should probably start implementing this instead of logging to a file.

Code reviewed and merged into develop branch with commit 95589d0bbe01c27e4ce7812bef8582bf4fec9343

Log in to comment on this ticket.

Metadata