Verbose 1 is giving too much detail (IMO) #137

New Issue

clickwir · 2019-01-26T20:05:57Z

clickwir commented

2019-01-26 20:05:57 +00:00

I've been using 'verbose 1' for a long time and like it's output. But after updating borgmatic on a few systems, I've noticed they are giving a lot more output. It seems 'verbose 1' now gives output for every file it touches.

While this is fine for those wanting more detail, I feel that verbosity level 1 shouldn't. Level 0 gives almost no useful output other than "Start" and "Stop" and any errors. Which is also fine for that level. What I want is a little more than level 0, which is what we used to get, a nice summary of size, dedupe, compression, how much was gained or removed for pruning vs new backups.

But now the daily emails are thousands of lines long and we have to scroll a lot to get to the useful summary info.

Is this an oversight or bug or just a new way of doing verbose? If this is a new way, I'd like to request something like a Level 0.5, something in between nothing and way too much.

I've seen this on at least 5 systems that we've recently updated borgmatic on.

I've been using 'verbose 1' for a long time and like it's output. But after updating borgmatic on a few systems, I've noticed they are giving a lot more output. It seems 'verbose 1' now gives output for every file it touches. While this is fine for those wanting more detail, I feel that verbosity level 1 shouldn't. Level 0 gives almost no useful output other than "Start" and "Stop" and any errors. Which is also fine for that level. What I want is a little more than level 0, which is what we used to get, a nice summary of size, dedupe, compression, how much was gained or removed for pruning vs new backups. But now the daily emails are thousands of lines long and we have to scroll a lot to get to the useful summary info. Is this an oversight or bug or just a new way of doing verbose? If this is a new way, I'd like to request something like a Level 0.5, something in between nothing and way too much. I've seen this on at least 5 systems that we've recently updated borgmatic on.

witten commented

2019-01-26 21:31:06 +00:00

Assuming that the list of files you're seeing is only the list of changed files, this is an intentional change rather than a bug. This new way of doing verbosity happened in borgmatic 1.2.3. From the changelog:

#64, #90, #92: Rewrite of logging system. Now verbosity flags passed to Borg are derived from borgmatic's log level. Note that the output of borgmatic might slightly change.

Please feel free to check out any of those tickets for more details.

However, in borgmatic 1.2.13, a --stats option was added:

#100: Support for --stats command-line flag independent of --verbosity.

So with recent versions of borgmatic, you can try --verbosity 0 in combination with --stats to see if that's closer to the old behavior you're looking for. In any case, please let me know!

Assuming that the list of files you're seeing is only the list of *changed* files, this is an intentional change rather than a bug. This new way of doing verbosity happened in borgmatic 1.2.3. From the changelog: > \#64, \#90, \#92: Rewrite of logging system. Now verbosity flags passed to Borg are derived from borgmatic's log level. Note that the output of borgmatic might slightly change. Please feel free to check out any of those tickets for more details. However, in borgmatic 1.2.13, a `--stats` option was added: > \#100: Support for --stats command-line flag independent of --verbosity. So with recent versions of borgmatic, you can try `--verbosity 0` in combination with `--stats` to see if that's closer to the old behavior you're looking for. In any case, please let me know!

witten added the

question / support

label 2019-01-26 21:31:12 +00:00

clickwir commented

2019-01-27 16:18:42 +00:00

Ok, sounds possible...

So I removed '-v 1' and added '--stats'. Now I get errors.

Traceback (most recent call last):
File "/usr/local/bin/borgmatic", line 11, in
sys.exit(main())
File "/usr/local/lib/python3.6/dist-packages/borgmatic/commands/borgmatic.py", line 355, in main
args = parse_arguments(*sys.argv[1:])
File "/usr/local/lib/python3.6/dist-packages/borgmatic/commands/borgmatic.py", line 170, in parse_arguments
raise ValueError('The --stats option can only be used with the --create or --prune options')
ValueError: The --stats option can only be used with the --create or --prune options

What I've been doing is just running borgmatic with no options except '-v 1'. So that it would run through all 3, prune, create, check.

I guess now I'm going to have to figure out yet another script wrapper to run all of them one at a time. Less than ideal.

Ok, sounds possible... So I removed '-v 1' and added '--stats'. Now I get errors. Traceback (most recent call last): File "/usr/local/bin/borgmatic", line 11, in <module> sys.exit(main()) File "/usr/local/lib/python3.6/dist-packages/borgmatic/commands/borgmatic.py", line 355, in main args = parse_arguments(*sys.argv[1:]) File "/usr/local/lib/python3.6/dist-packages/borgmatic/commands/borgmatic.py", line 170, in parse_arguments raise ValueError('The --stats option can only be used with the --create or --prune options') ValueError: The --stats option can only be used with the --create or --prune options What I've been doing is just running borgmatic with no options except '-v 1'. So that it would run through all 3, prune, create, check. I guess now I'm going to have to figure out yet another script wrapper to run all of them one at a time. Less than ideal.

witten commented

2019-01-27 19:11:47 +00:00

Well that's silly! 😄 Why don't I make the argument parsing exception you mention above more surgical, so that it allows borgmatic --stats even without specifying particular --create or --prune flags?

Well that's silly! :smile: Why don't I make the argument parsing exception you mention above more surgical, so that it allows `borgmatic --stats` even without specifying particular `--create` or `--prune` flags?

witten commented

2019-01-27 20:07:47 +00:00

Filed #138 to better handle that situation.