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.

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

Add logging to manage.py commands used as cronjobs #876

Open
Kurocon opened this issue Jun 17, 2024 · 0 comments
Open

Add logging to manage.py commands used as cronjobs #876

Kurocon opened this issue Jun 17, 2024 · 0 comments
Labels
back-end These are issues related to our Django back-end easy-to-fix These issues are easy to fix and recommended for newer members. enhancement These issues are enhancements to (already existsing) functionality on the website.

Comments

@Kurocon
Copy link
Member

Kurocon commented Jun 17, 2024

When amelie was running on regular servers, we needed to keep the cronjob tasks silent, because all output would be e-mailed to the www-supers.
Now that we are running on Kubernetes, cronjobs are running as Kubernetes Jobs, and they can log to standard output normally. Logs can be viewed via the Kubernetes dashboard. However these are very quiet now.

We should add some logging to see what our cronjob tasks are doing.

@Kurocon Kurocon added enhancement These issues are enhancements to (already existsing) functionality on the website. back-end These are issues related to our Django back-end easy-to-fix These issues are easy to fix and recommended for newer members. labels Jun 17, 2024
@supertom01 supertom01 moved this from Backlog to Ready in WWW - Sprint board Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
back-end These are issues related to our Django back-end easy-to-fix These issues are easy to fix and recommended for newer members. enhancement These issues are enhancements to (already existsing) functionality on the website.
Projects
Status: Ready
Development

No branches or pull requests

1 participant