We need to move Graphoid 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 | |||
| Declined | None | T219923 Move graphoid logging to new logging pipeline |
Event Timeline
Comment Actions
Apparently graphoid is still using service::node::config and not the config template in the deployment repo. Given that graphoid will be switched to k8s soon, should we just postpone this until the switch, move graphoid to deployment-repo config or do the puppet work to enable rsyslog in service::node::config? What do you think @akosiaris @fgiunchedi @mobrovac ?
Comment Actions
I think it's ok to leave it as-is until the move to k8s, but will defer to @akosiaris and @fgiunchedi whether the timelines work for them.
Comment Actions
Given that graphoid will be switched to k8s soon,
It will? We are still waiting on T211881 for an owner for the service to appear before that is even considered.
should we just postpone this until the switch, move graphoid to deployment-repo config or do the puppet work to enable rsyslog in service::node::config? What do you think @akosiaris @fgiunchedi @mobrovac ?
I would postpone any work until T211881 is completed tbh, unless we can't do otherwise.