Page MenuHomePhabricator

Logging system needs to be improved
Open, NormalPublic

Description

Thanks again, Graham K:

there are problems with "view log file" when it gets large

Yes, there are. I have some ideas about a system that's more of a logging database (well, I've used systems that do logging better -- I didn't come up with any new ideas, yet)

Event Timeline

Joe created this task.Jan 30 2018, 10:02 PM
Joe created this object in space S5 Public.
Joe created this object with visibility "Public (No Login Required)".
Joe added a comment.Jul 12 2018, 3:30 PM

JW C:

  1. The job run log might be re-organized a little differently to:
    • Somehow better separate each job data set so one can see better the beginning of each job data set quickly. Maybe set up so one can use the keyboard page up/down keys to have it stop at each job data set start?
    • Move any job errors list (now in red text) to the beginning of a job data set so one can more quickly find what the problems were.
Joe added a comment.Feb 22 2019, 10:20 AM

Peter wrote:

Optional log of file names that could not be replicated.

Joe raised the priority of this task from Wishlist to Normal.Feb 22 2019, 10:21 AM
Joe added a comment.Feb 22 2019, 11:54 AM

Mike wrote:

I liked to know how many files were accessed during the backup process, how many were backed up (perhaps individual file sizes listed), how many were bypassed (incremental backups, etc.), number files from previous backups, etc.