Feature Request - Time stamps in job processing overview

[TommyB]

Hi,

just like in the "bigger" Veeam products, there is one important thing missing in the job progress overview, the point in time when the actual entry was created.

There are only "action" and "duration" columns.

Thomas

[Dima P.]

Thomas,
To get the exact date you can click the column and see the detailed info.

[Gostev]

Dmitry - we need to add summary info balloon as user hovers over those columns, and say "Click for more info" at the bottom of summary (our original design plan), as most people are unable to guess that the columns are click-able. Thanks!

[Dima P.]

Anton,
Already in development

[Gostev]

Muy bueno

[TommyB]

Thomas,
To get the exact date you can click the column and see the detailed info.

Hmm... nothing happens when I click on any entry or the column header (which briefly flashes in green).

The only way to get details for an entry is to right click, select "copy top clipboard" and paste into notepad or something similar.

It then shows something like this:

16.12.2014 09:27:52 :: SYSTEM (disk 0) (100,0 MB) 62,0 MB read at 62 MB/s

[Dima P.]

In the bottom of the session log - processing finished at date XX:XX

[TommyB]

In the bottom of the session log - processing finished at date XX:XX

well... but that is only shown when the job is finished and it does not show the time of each log entry.

I just found that Veeam 8 works the same way, right-click and copy-paste the entry into notepad reveals the time stamp.

So please, either add another column (there is plenty of room IMHO) or add the time stamp to the tool tip that shows when hovering over an entry.

By the way that tool tip currently is quite useless because it only shows the same information that is already there (which is the same for Veeam 8 and Endpoint backup).

[aaron@ARB]

Sorry to bring up an old feature request but was this relating to in the job


You can see when you have long jobs like backing up to tape, knowing at what time "Failed to backup some full backup files, skipping the corresponding incremental backup" actually happened so that you can then trawl the logs for answers.

Did this request get implemented / or is this something different. Either way i think it would be valuable from a debugging perspective if nothing else.

[TommyB]

I'd like to push this again... an action log without time stamps is not very useful.

[Dima P.]

Hi TommyB,

Info balloon with timestamp was implemented, as promised (hover mouse over the bar chart to see the date). Nothing changed regarding the timestamp in backup log but thanks for pushing. I’ll discuss it with the team.

[aaron@ARB]

Hi Dima,
Any chance of having timestamps in the line by line as i asked for up a little... having a tooltip which just shows you what you can already read isn't all that useful at the moment, tacking on the date/time would however make debugging and checking he log files infinitely more useful (and I think your support would probably appreciate it also)

[Dima P.]

Hi Aaron,

To be honest, I don’t like the idea of adding timestamp for each log event - it makes the log hard to read, for regular users who does not need this information. That said, I like the idea of adding the timestamp to the balloon for every event. If that works for you, I’ll discuss it with the dev team.

[aaron@ARB]

hi Dima,

Not a problem, makes perfect sense, I'm fine with that.... Just something that makes it available to those who need to see it for debugging purposes. I think your support teams will get more use out of it than customers will but there have been times when I am trying to work through an issue and correlating what the job log says vs what the actual log files are saying.

Cheers,
Aaron

[Dima P.]

Thanks! I'll talk to the devs but can’t promise we will add this to the upcoming version.

[TommyB]

Hi Aaron,

To be honest, I don’t like the idea of adding timestamp for each log event - it makes the log hard to read, for regular users who does not need this information.

I read "Regular users" as "Backup Admins"... Admins should not be confused by date/timestamps... otherwise they should look for a different, maybe less confusing, job

The timestamp IMHO is the second important data of a log entry.

But if adding the date/time to the tooltip/balloon can be programmed faster than a separate column, I'm fine with that as well

[Dima P.]

Hi Thomas,

Thanks. Thats the plan.