-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Logging of statusengine #15
Comments
I would prefer to use SysLog so that Statusengine don't need to take care about log rotation and stuff like this. |
Now the error output is back on stderr: I changed syslog tag from Statusengine to statusengine so it's easy to grep for it. (After i took the screenshots...) In the next step i will remove the LogfileTask. |
Sounds great |
Statusengine is now using syslog as "statusengine" to resolve the issue #15 so Statusengine dont need to care about log rotating and stuff like this
Merged into new Version 1.6.0 |
I've realized different things with the logging of statusengine cakephp application
The LegacyShell Daemon uses a hardcoded file handler to write the output to
The current hardcoded file handler logging doesn't log any timestamps in the logfile which makes it harder to analyse future possible problems or crashes.
The current code doesn't support logfile rotation. StatusengineLegacyShell.php could reopen (close/open) the logfile on SIGHUP or similar to support log rotation.
CakePHP provides a generic LogHandlerInterface which supports file, syslog and other handler. Is there a reason for not using the generic logging interface instead of fopen/fwrite? With generic logging and syslog you would tackle the logrotation problem also since logrotation can be taken care on the syslog server, etc
The text was updated successfully, but these errors were encountered: