Skip to content

More consistent logging: severity missing #969

@afreudenreich

Description

@afreudenreich

When I try to request a certificate for a domain, which fails a DNS lookup, I get following output:

2019/09/17 12:25:45 [INFO] [<bad.domain>] AuthURL: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/8733359
2019/09/17 12:25:45 [INFO] [<bad.domain>] acme: Could not find solver for: tls-alpn-01
2019/09/17 12:25:45 [INFO] [<bad.domain>] acme: use http-01 solver
2019/09/17 12:25:50 [INFO] [<bad.domain>] acme: Trying to solve HTTP-01
2019/09/17 12:25:50 [INFO] Unable to deactivate the authorization: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/8733359
2019/09/17 12:25:50 Could not obtain certificates:
	acme: Error -> One or more domains had a problem:
[<bad.domain>] acme: error: 400 :: urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up A for <bad.domain>, url: 

For easier log parsing the last entry should at least contain the severity in square brackets. E.g. like this:

2019/09/17 12:25:50 [ERROR] Could not obtain certificates:...

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions