@mobrovac I just noticed in the description the newest version of service-runner part. We currently run 2.6.7, is it enough?
Eh no, unfortunately not. Support for prefixed syslog logging came in v2.6.15. The [diff between v2.6.7 and v2.6.15](https://github.com/wikimedia/service-runner/compare/v2.6.7...v2.6.15) suggests it's safe for you to update to that version. Moreover, it would beneficial if you could update to the latest version, v2.7.3 as it brings many improvements and bug fixes over v2.6.15. Again, the diff suggests there are no backwards-incompatible interface changes, so you should fine in doing so.
|Open||None||T227080 Deprecate all non-Kafka logstash inputs|
|Invalid||None||T225122 Migrate services using deprecated Gelf logstash input to Kafka enabled logging pipeline|
|Open||None||T225125 Migrate Elasticsearch from deprecated Gelf logstash input to rsyslog Kafka logging pipeline|
|Open||Pchelolo||T211125 Move service-runner to new logging infrastructure|
|Resolved||elukey||T219928 Move AQS logging to new logging pipeline|
|Resolved||Milimetric||T236757 Upgrade service-runner on AQS to unblock rsyslog logging|
I think we can safely skip this. We're going to be updating service-runner based services to be prometheus-native (see https://github.com/wikimedia/service-runner/pull/221), so we can leapfrog this.
@Milimetric you can just update the service-runner version, but it would probably be better to use this as an opportunity to do so by updating to the latest service-template-node: