Send tink-worker logs to stdout instead of stderr:

[jacobweinstock]

Description

In HookOS, normally, all Docker logs are sent via syslog to Smee. When a container writes its logs to stderr the Docker syslog driver will set the severity to "ERR". This then shows up in Smee's logs. User are consistently confused as to what this severity means and more often than not, they believe the log line to be an error. By writing tink-worker logs to stdout the severity in syslog will be "INFO".

Examples:

Before:

{"level":"info","ts":1699046587.4014122,"caller":"syslog/receiver.go:160","msg":"msg","msg":{"app-name":"e89e8c7e84ba","facility":"daemon","host":"10.42.0.15","msg":{"caller":"cmd/root.go:53","level":"info","logger":"github.com/tinkerbell/tink","msg":"starting","ts":1699046585.7805724,"version":"devel"},"procid":"736","severity":"ERR"}}
{"level":"info","ts":1699046587.4016318,"caller":"syslog/receiver.go:160","msg":"msg","msg":{"app-name":"e89e8c7e84ba","facility":"daemon","host":"10.42.0.15","msg":{"caller":"worker/worker.go:249","level":"info","logger":"github.com/tinkerbell/tink","msg":"starting to process workflow actions","ts":1699046585.7809546,"workerID":"52:54:00:0f:2e:67"},"procid":"736","severity":"ERR"}}

After:

{"level":"info","ts":1699047980.6784308,"caller":"syslog/receiver.go:160","msg":"msg","msg":{"app-name":"947f1fb0d32c","facility":"daemon","host":"10.42.0.15","msg":{"caller":"cmd/root.go:55","level":"info","logger":"github.com/tinkerbell/tink","msg":"starting","ts":1699047979.8558161,"version":"devel"},"procid":"738","severity":"INFO"}}
{"level":"info","ts":1699047980.6787195,"caller":"syslog/receiver.go:160","msg":"msg","msg":{"app-name":"947f1fb0d32c","facility":"daemon","host":"10.42.0.15","msg":{"caller":"worker/worker.go:249","level":"info","logger":"github.com/tinkerbell/tink","msg":"starting to process workflow actions","ts":1699047979.8561027,"workerID":"52:54:00:0f:2e:67"},"procid":"738","severity":"INFO"}}

Why is this needed

Fixes: #

How Has This Been Tested?

How are existing users impacted? What migration steps/scripts do we need?

Checklist:

I have:

• updated the documentation and/or roadmap (if required)
• added unit or e2e tests
• provided instructions on how to upgrade

[codecov]

Codecov Report

Merging #833 (96dd4fd) into main (a9b0899) will not change coverage.
The diff coverage is n/a.

❗ Current head 96dd4fd differs from pull request most recent head e124c55. Consider uploading reports for the commit e124c55 to get more accurate results

@@           Coverage Diff           @@
##             main     #833   +/-   ##
=======================================
  Coverage   51.16%   51.16%           
=======================================
  Files          33       33           
  Lines        1456     1456           
=======================================
  Hits          745      745           
  Misses        665      665           
  Partials       46       46           

📣 Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today!