Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: nice readable backup summary print #1156

Open
mrlee14 opened this issue May 17, 2024 · 6 comments · May be fixed by #1159
Open

Feature request: nice readable backup summary print #1156

mrlee14 opened this issue May 17, 2024 · 6 comments · May be fixed by #1159
Labels
C-question Category: Further information is requested

Comments

@mrlee14
Copy link

mrlee14 commented May 17, 2024

personalty would appreciate summary at the and of backup, in a simple readable text format, of what was done so far, the essential details....

@github-actions github-actions bot added the S-triage Status: Waiting for a maintainer to triage this issue/PR label May 17, 2024
@mrlee14 mrlee14 changed the title Feature request: nice readable summary print Feature request: nice readable backup summary print May 17, 2024
@aawsome
Copy link
Member

aawsome commented May 17, 2024

@mrlee14 Can you please give some more details? What kind of information are you missing?

Do you know about rustic backup --json and rustic snapshots --long / rustic snapshots --json?

@simonsan simonsan added C-question Category: Further information is requested and removed S-triage Status: Waiting for a maintainer to triage this issue/PR labels May 17, 2024
@mrlee14
Copy link
Author

mrlee14 commented May 19, 2024

@mrlee14 Can you please give some more details? What kind of information are you missing?

Do you know about rustic backup --json and rustic snapshots --long / rustic snapshots --json?

OK, I see all details and so on.., maybe the option to disable '[INFO]' lines on cli backup cmd and print only 'backing up...' lines, less verbose, its perhaps already configurable?...

@mrlee14
Copy link
Author

mrlee14 commented May 19, 2024

@mrlee14 Can you please give some more details? What kind of information are you missing?
Do you know about rustic backup --json and rustic snapshots --long / rustic snapshots --json?

OK, I see all details and so on.., maybe the option to disable '[INFO]' lines on cli backup cmd and print only 'backing up...' lines, less verbose, its perhaps already configurable?...

its not truly necessary, as is is already very good...

@aawsome
Copy link
Member

aawsome commented May 21, 2024

@mrlee14 I already heard other users that the output verbosity should be discussed and maybe changed. So far, you can use --level= to set the output verbosity, the default is info. Do you think we should start a discussion about better verbosity and better defaults?

About the summary output: We can easily add a --long option to the backup command which would output the summary like snapshots is currently doing. Would you see this as valuable?

@mrlee14
Copy link
Author

mrlee14 commented May 21, 2024

@mrlee14 I already heard other users that the output verbosity should be discussed and maybe changed. So far, you can use --level= to set the output verbosity, the default is info. Do you think we should start a discussion about better verbosity and better defaults?

About the summary output: We can easily add a --long option to the backup command which would output the summary like snapshots is currently doing. Would you see this as valuable?

Yes, I think this would be very interesting to have at the bottom of backup, nicely formatted…

@aawsome aawsome linked a pull request May 28, 2024 that will close this issue
@intgr
Copy link

intgr commented Jun 14, 2024

Something that I would find extremely useful in output is a summary of what is expanding my repository size. I couldn't care less about some extra megabytes per snapshot, but if I keep accidentally adding stuff to backup that I don't want there, it may eventually get in trouble with my cloud storage quota.

So maybe:

  • A summary of new directories/paths added compared to previous backup, if their size exceeds a threshold. E.g. if I have cloned a git repo at ~/git/linux, which adds 6 GB to the Rustic repository, I'd like to know immediately so I can adjust my ignore rules and delete that snapshot. To be useful, this should be the size of the whole directory including all files recursively.

  • Similarly, if an existing file has a large amount of changes, it would be nice to know about that (e.g. I have a VM disk image included in backups and I made lots of changes in that VM). Ideally Rustic would summarize it per directory if there are changes to lots of small changes to files in a single directory, but that may require some complicated heuristics.

    • For some use cases, lots of changes is to be expected, so perhaps this should be a "top 5" or "top 10" list, and a reasonable size threshold as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-question Category: Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants