`cloud-init analyze` depends on the upstream-shipped log format to function

This bug was originally filed in Launchpad as [LP: #1876794](https://bugs.launchpad.net/cloud-init/+bug/1876794)

Launchpad details

affected_projects = []

assignee = None

assignee_name = None

date_closed = None

date_created = 2020-05-04T19:10:15.977143+00:00

date_fix_committed = None

date_fix_released = None

id = 1876794

importance = medium

is_complete = False

lp_url = https://bugs.launchpad.net/cloud-init/+bug/1876794

milestone = None

owner = oddbloke

owner_name = Dan Watkins

private = False

status = triaged

submitter = oddbloke

submitter_name = Dan Watkins

tags = []

duplicates = []

_Launchpad user **Dan Watkins(oddbloke)** wrote on 2020-05-04T19:10:15.977143+00:00_

This is a more general version of bug 1876323: `cloud-init analyze` relies on the log format that upstream ships in order to detect log lines. This means that if logging configuration by users or downstream packagers diverges (as is the case on Amazon Linux 2, for example), then the `analyze` commands will not produce any useful output (or a useful error message).

(Ubuntu uses this log format, so this bug does not present on Ubuntu.)