Finer grained verbosity levels #194
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#194
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 anyborg
output shown relates, or - when used with--verbosity 1
- there is both the desired information likeREPO: 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.
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.
From #borgmatic IRC:
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.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.