We have 3 issues with our coworker logging at the moment -
1) my current issue - there is no enough detail hitting the syslog to determine why it is failing on staging. I have an upstream patch (which will hopefully merge quickly) to address that https://lab.civicrm.org/dev/coworker/-/merge_requests/7 (which would probably make the request to @Dwisehaupt to set staging to use the log-to-file flag redundant). However if we want to test it on staging we would need to download the phar per https://lab.civicrm.org/dev/coworker/-/blob/master/doc/develop.md - ideally we would test it there before leaning on Tim to put out a formal release
2) when we log from CiviCRM for command line based activity we log to stdout. This causes problems with coworker. Tim suggested that we could log to stderr instead. This is an easy codechange but I need to check in with @Dwisehaupt what the impact of switching from stdout to stderr would be on our job logs & with @ejegg / others if it would impact our practices. Alternatively we could detect coworker and log to stderr rather than stdout conditionally. I suspect logging to stderr in general is more correct but I'm not sure if it would impact us
3) we overlog information from coworker - this might be purely as a result of 2 - ie we ignore these errors "
Jan 23 12:45:17 coworker[1448965]: #033[31m[2024-01-23T12:45:17.882285+00:00] Pipe[ctl#1].ERROR: Received unexpected response line: "{"jsonrpc":"2.0","result":[],"id":667944}"#033[0m" - Tim suggested we don't worry about this until 2 is resolved
Links
Upstream issue https://lab.civicrm.org/dev/coworker/-/issues/13
Phar publishing https://lab.civicrm.org/dev/coworker/-/blob/master/doc/develop.md