Finer grained verbosity levels #194

Closed
opened 2019-06-16 18:05:32 +00:00 by elho · 3 comments

When using /etc/borgmatic.d with multiple configs for multiple archives, there either is no indication at all, which of them is currently being processed and thus to which any borg output shown relates, or - when used with --verbosity 1 - there is both the desired information like REPO: Listing archives and several other, arguably more verbose, lines that are undesired in this use case like /etc/borgmatic.d/foo.yaml: Parsing configuration file.

Verbosity lveel 1 should only show the former, verbosity level 2 what 1 shows now, etc.

When using `/etc/borgmatic.d` with multiple configs for multiple archives, there either is no indication at all, which of them is currently being processed and thus to which any `borg` output shown relates, or - when used with `--verbosity 1` - there is both the desired information like `REPO: Listing archives` and several other, arguably more verbose, lines that are undesired in this use case like `/etc/borgmatic.d/foo.yaml: Parsing configuration file`. Verbosity lveel 1 should only show the former, verbosity level 2 what 1 shows now, etc.
Owner

What do you think of just demoting the less desirable log entries like Parsing configuration file to the debug level so that they only show up in verbosity level 2? That would leave more of the useful stuff at verbosity level 1.

If you think that could work, then it'd be good to know what other log entries you don't find terribly useful.

What do you think of just demoting the less desirable log entries like `Parsing configuration file` to the debug level so that they only show up in verbosity level 2? That would leave more of the useful stuff at verbosity level 1. If you think that could work, then it'd be good to know what other log entries you don't find terribly useful.
Owner

From #borgmatic IRC:

elho | witten: Gotta use borgmatic a bit more before I can comment on the usefulness of other verbose messages :)

So what I think I'll do for this ticket is do a brief audit of the existing .info() log message, demoting some of them to .debug() as I see fit.

From #borgmatic IRC: > elho | witten: Gotta use borgmatic a bit more before I can comment on the usefulness of other verbose messages :) So what I think I'll do for this ticket is do a brief audit of the existing `.info()` log message, demoting some of them to `.debug()` as I see fit.
witten added the
design finalized
label 2019-06-17 19:01:12 +00:00
Owner

Well, I audited all logger.info() invocations, and only ended up demoting the one log entry you called out above. So I'll close this for now, but if you can come up with other examples I'd be happy to demote them as well if that makes sense.

Well, I audited all `logger.info()` invocations, and only ended up demoting the one log entry you called out above. So I'll close this for now, but if you can come up with other examples I'd be happy to demote them as well if that makes sense.
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#194
No description provided.