Comment 3 for bug 1838032

cloud-init does not write to syslog by default because it wants to
allow the user to configure rsyslog. second difference/tidyness thing
is that /var/log/cloud-init.log contains DEBUG output. I does not
feel proper to me to have debug output written to syslog (or journal)
by default.

cloud-init needs lots of cleanup on logging. it is really verbose in
most cases with output not suitable or useful to the journal.

On Mon, Jul 29, 2019 at 2:10 PM Dan Watkins
<email address hidden> wrote:
>
> We just had some internal conversation about this, which I will do my
> best to summarise here.
>
> Ryan agreed that this would make debugging easier, but worried about
> removing cloud-init.log as it's a well established path that people rely
> on. He identified that `cloud-init analyze` was one example of
> something that would need to be modified to not rely on cloud-init.log.
>
> I noted that I wasn't intending this as a proposal to drop cloud-
> init.log. I noted that we're going to need to support non-systemd
> instances using cloud-init.log anyway, so we won't be able to drop those
> code paths regardless. I noted that `cloud-init collect-logs` may need
> updating.
>
> I proposed the following plan for Ubuntu: emit to both cloud-init.log
> and the journal in 20.04 LTS, and discuss dropping cloud-init.log for
> 22.04 LTS.
>
> --
> You received this bug notification because you are subscribed to cloud-
> init in Ubuntu.
> https://bugs.launchpad.net/bugs/1838032
>
> Title:
> cloud-init should emit all of its logs to the systemd journal
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1838032/+subscriptions