Yes that would be the intention of “adding proper logging”.
No, this was/is “the issue” with both emonhub and service-runner, both are being resolved by taking control of the output and placing it where we want it before systemd/journald gets hold of it. Even if just for “consistency” we shouldn’t do what we have already ruled out for the other services!
Just a thought now I’ve said that out loud (or rather, typed it out loud?) this is another common factor to emonhub and service-runner besides the fact they are both Python. But the fact they both use an OEM designed service unit and just leave stdout and stderr for the system to handle! (Ref the Emonhub fails to start - #17 by borpin thread).