We need to move Proton to the new logging pipeline. The config should be updated similar to https://gerrit.wikimedia.org/r/#/c/mediawiki/services/change-propagation/deploy/+/500813 and newest node dependencies should be used (newest version of service-runner.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | herron | T227080 Deprecate all non-Kafka logstash inputs | |||
| Invalid | None | T225122 Migrate services using deprecated Gelf logstash input to Kafka enabled logging pipeline | |||
| Resolved | herron | T225125 Migrate Elasticsearch from deprecated Gelf logstash input to rsyslog Kafka logging pipeline | |||
| Resolved | • Pchelolo | T211125 Move service-runner to new logging infrastructure | |||
| Invalid | None | T224602 Fix logging umbrella task | |||
| Resolved | fgiunchedi | T219925 Move proton logging to new logging pipeline | |||
| Resolved | akosiaris | T239459 service-runner apps running on kubernetes emit logs with log level 50 |
Event Timeline
Comment Actions
Reminder/ping as we (SRE Observability) would like to deprecate all non-kafka inputs by end of Q4 FY19/20. If the service is moving (or has moved) to k8s then what's left to do is disable gelf log output and keep on stdout/stderr. If the service isn't moving to k8s then we'll also need to perform puppet-level changes. Thanks!
Comment Actions
Stalling since we'll be piggybacking on Proton (and mobileapps) moving to k8s, and thus the logging pipeline. See also T219924 for the full discussion.
Comment Actions
Looks like mobileapps has been fixed in T219924, though I'm not seeing any logging configuration for proton in the deployment-charts repository (nor proton logs) yet
Comment Actions
It looks like mobileapps and proton (chromium-render) have essentially the same logging config (see https://gerrit.wikimedia.org/r/plugins/gitiles/operations/deployment-charts/+/refs/heads/master/charts/mobileapps/templates/_config.yaml and https://gerrit.wikimedia.org/r/plugins/gitiles/operations/deployment-charts/+/refs/heads/master/charts/chromium-render/templates/_config.yaml):
# Logger info
logging:
level: warn
name: <name of service>
streams:
- type: stdout
named_levels: trueComment Actions
Thank you for the update @Mholloway ! That indeed clears up things and I can see proton/chromium-render logs coming through the logging pipeline. I'm boldly resolving the task, though please reopen if something is amiss!