action #135482
Updated by okurz 7 months ago
## Motivation
While investigating #135122 we noticed that there is currently no log file for the websocket server. Despite one existing for each of the other openQA services on the OSD webui (`/var/log/openqa`, `/var/log/openqa_gru`, `/var/log/openqa_scheduler`). This is currently getting in the way because we can't just add new log messages to the websocket server to help with debugging. Searching the journal for specific log messages is almost impossible since it is too slow.
## Acceptance criteria
* **AC1:** We use system journal only for o3+osd or we know why we don't A `/var/log/openqa_websockets` log file exists on OSD.
* **AC2:** The websocket server log file is logrotated.
## Suggestions
* Optional: Research in old tickets why we chose explicit log files over just trusting systemd journal
* As by default openQA and all related tooling already just use the systemd service we shouldn't need to implement anything in upstream openQA itself, just change the config accordingly
* - Just disable log files for all openQA related services on o3 and see what happens
* After positive result do replicate the same setup for OSD
* Ensure that all openQA related services still run as expected
* Ensure that our system journal shows results from all according openQA services for a sufficient amount `/var/log/openqa_scheduler` in salt.
## Out of time, at least 7 days or so scope
* Look into how logwarn can access - Fixing `/var/log/openqa`, which also currently goes to the journal, either just configure journald to write to a logfile and point logwarn to that, or if it's too much effort create dedicated ticket journal.
Back