After I upgraded the client package to the py3 version in bionic, while testing https://github.com/CanonicalLtd/landscape-client/pull/27 (which worked, btw), the client log files all got a "landscape-" prefix:
drwxr-xr-x 2 landscape root 14 Jan 19 19:49 .
drwxrwxr-x 8 root syslog 18 Jan 19 19:32 ..
-rw------- 1 landscape landscape 11K Jan 19 19:49 broker.log
-rw------- 1 landscape landscape 2.2K Jan 19 19:55 landscape-broker.log
-rw-r--r-- 1 root landscape 77 Jan 19 19:49 landscape-client.log
-rw------- 1 root root 1.4K Jan 19 19:55 landscape-manager.log
-rw------- 1 landscape landscape 3.8K Jan 19 19:55 landscape-monitor.log
-rw------- 1 landscape landscape 380 Jan 19 19:50 landscape-package-reporter.log
-rw------- 1 landscape landscape 3.8K Jan 19 19:49 manager.log
-rw------- 1 landscape landscape 11K Jan 19 19:49 monitor.log
-rw------- 1 landscape landscape 113 Jan 19 19:50 package-changer.log
-rw------- 1 landscape landscape 5.2K Jan 19 19:47 package-reporter.log
-rw-r--r-- 1 landscape landscape 0 Jan 19 19:33 sysinfo.log
-rw-r--r-- 1 landscape landscape 284 Jan 19 19:49 watchdog.log
This is surprising for users, but the biggest impact mid-term is the logrotate rules, which won't catch this change:
/etc/logrotate.d/landscape-client:
/var/log/landscape/watchdog.log /var/log/landscape/monitor.log /var/log/landscape/broker.log /var/log/landscape/manager.log {
...
/var/log/landscape/package-changer.log /var/log/landscape/package-reporter.log /var/log/landscape/sysinfo.log /var/log/landscape/release-upgrader.log {
https:/