Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Raise level of occuring cron events to INFO #34

Closed
dnaber-de opened this issue Apr 30, 2018 · 0 comments
Closed

Raise level of occuring cron events to INFO #34

dnaber-de opened this issue Apr 30, 2018 · 0 comments

Comments

@dnaber-de
Copy link
Member

dnaber-de commented Apr 30, 2018 •
edited
Loading

Right now, the CronDebugListener records every cron worker event with the DEBUG severity:

[2018-04-30 14:32:21] DEBUG.DEBUG: Cron action "wp_scheduled_auto_draft_delete" performed.

Monitoring the proper execution of cron events is a typical scope of logging especially on production systems. Therefore I would suggest to raise the severity level to INFO as it is a normal operation without significant condition. Normally the threshold for log records for production environments is set to something above DEBUG to reduce the noise but right now this removes also the cron event log completely.

For sake of consistency the listener class should be renamed too, but this is way more invasive as it is considered public API, I guess?
@dnaber-de dnaber-de mentioned this issue Apr 30, 2018
Merged
gmazzap added a commit that referenced this issue Apr 30, 2018
@gmazzap
Merge pull request #35 from inpsyde/issue-34-cron-severity
a599964 
Raise log level for cron events to INFO. Fixes #34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dnaber-de