action #57239
Updated by okurz over 2 years ago
## Motivation
Just as o3-admins@suse.de we have a mailing list osd-admins@suse.de now which is used for example for grafana monitoring messages. But o3:/etc/openqa/openqa.ini was changed to not write log messages to /var/log/openqa anymore but all to the journal, meaning that openqa_logwarn does not work anymore as in before.
## Acceptance criteria
* **AC1:** A periodic job for openqa_logwarn sends (again) emails if any unexpected errors are encountered in service logs on o3, sent to o3-admins@suse.de
* **AC2:** Same as *AC1* but on osd, sent to osd-admins@suse.de
## Suggestions
* Research what https://github.com/os-autoinst/openqa-logwarn is doing
* Lookup cron job or systemd timer definitions on o3 and/or osd to find out how this should be triggered
* Test if simple email sending from crontab works
* Look on o3 and osd what the output of openqa_logwarn is and ensure that emails are sent if there are unexpected errors encountered in logfiles Will create follow-up ticket.
Just as o3-admins@suse.de we have a mailing list osd-admins@suse.de now which is used for example for grafana monitoring messages. But o3:/etc/openqa/openqa.ini was changed to not write log messages to /var/log/openqa anymore but all to the journal, meaning that openqa_logwarn does not work anymore as in before.
## Acceptance criteria
* **AC1:** A periodic job for openqa_logwarn sends (again) emails if any unexpected errors are encountered in service logs on o3, sent to o3-admins@suse.de
* **AC2:** Same as *AC1* but on osd, sent to osd-admins@suse.de
## Suggestions
* Research what https://github.com/os-autoinst/openqa-logwarn is doing
* Lookup cron job or systemd timer definitions on o3 and/or osd to find out how this should be triggered
* Test if simple email sending from crontab works
* Look on o3 and osd what the output of openqa_logwarn is and ensure that emails are sent if there are unexpected errors encountered in logfiles Will create follow-up ticket.