Change Details

Similarly to {T211124} this task is about tracking the necessary changes to `service-runner` to use the new logging infrastructure. The general transports/protocols involved are syslog + JSON, specifically a `@cee: ` token/cookie is required to prefix the json payload to properly recognize said message as json/structured logging (see also https://www.rsyslog.com/doc/v8-stable/configuration/modules/mmjsonparse.html). For transport the preferred way is through unix socket `/dev/log` (managed by journald, then messages are read by rsyslogd) though a compatibility udp endpoint can also be provided if needed.

Similarly to {T211124} this task is about tracking the necessary changes to `service-runner` to use the new logging infrastructure. The general transports/protocols involved are syslog + JSON, specifically a `@cee: ` token/cookie is required to prefix the json payload to properly recognize said message as json/structured logging (see also https://www.rsyslog.com/doc/v8-stable/configuration/modules/mmjsonparse.html). For transport the preferred way is through unix socket `/dev/log` (managed by journald, then messages are read by rsyslogd) though a compatibility udp endpoint can also be provided if needed. Additional information/context: https://wikitech.wikimedia.org/wiki/Logstash/SRE_onboard

Similarly to {T211124} this task is about tracking the necessary changes to `service-runner` to use the new logging infrastructure. The general transports/protocols involved are syslog + JSON, specifically a `@cee: ` token/cookie is required to prefix the json payload to properly recognize said message as json/structured logging (see also https://www.rsyslog.com/doc/v8-stable/configuration/modules/mmjsonparse.html). For transport the preferred way is through unix socket `/dev/log` (managed by journald, then messages are read by rsyslogd) though a compatibility udp endpoint can also be provided if needed. Additional information/context: https://wikitech.wikimedia.org/wiki/Logstash/SRE_onboard