-
Notifications
You must be signed in to change notification settings - Fork 377
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
Duplicate logging on RHEL/CentOS #740
Comments
@clangaxon Writing to the Console (aka /var/log/messages) is standard Linux practice, as is writing to a separate log file (e.g., /var/log/waagent.log). Admittedly, the agent has (and perhaps does still) emit too many messages. It is best that we address those issues vs. not writing to the standard locations. |
I can't think of many software packages that intentionally log everything twice with no user controls to avoid it. It'd be nice if you would: a) raise the logging threshold on console, or b) allow it to be disabled in the config, or c) package a systemd config that sent it to /dev/null. Thanks. |
@clangaxon We'll change the agent to only log warnings and errors to the console (aka /var/log/messages). That should reduce output. However, having it log to the Console is important for cloud instances since, at times, that is the only data available for diagnostics. |
@brendandixon thanks! |
We should review all messages emitted during GoalState processing and reduce their frequency. |
Addressed by #776 |
The agent logs to both the log file and stdout/stderr, so logs are duplicated in /var/log/waagent.log and /var/log/messages. This doubles the impact of #711
The text was updated successfully, but these errors were encountered: