public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Dominik Csapak <d.csapak@proxmox.com>,
	Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup 3/3] ui: datastore content: add action to show upload statistics
Date: Mon, 27 Nov 2023 11:27:10 +0100	[thread overview]
Message-ID: <13828147-47a3-44dd-9bc3-0451038c2a56@proxmox.com> (raw)
In-Reply-To: <895e307e-94f7-45d2-b094-f4fe464d4ae9@proxmox.com>

On 27.11.23 11:04, Dominik Csapak wrote:
>>> +		    getClass: (v, m, rec) => rec.data.ty === 'dir' ? 'fa fa-info-circle' : 'pmx-hidden',
>>
>> info-circle is not a good icon for some specific stats, i.e., not a
>> general info about the backup snapshot.. A stop-watch could be nice,
>> but there doesn't seem to be any, so possibly "fa-file-text-o" (a
>> sheet of stat lines, so to say), not ideal too but IMO better than
>> the info-circle.
>>
>> ps. maybe injecting some more general info like duration could be
>> nice (didn't check if we even have that available already here
>> though).
>>
>> That said maybe one could even make this an actual info dialog,
>> with the stats only be one part of that, then the info-circle
>> could be OK too and we'd not add a core UI element for a rather
>> niche information that most won't look at often.
> 
> here we basically have only the info we have in the grid already,
> but we could provide it in a nicer way maybe:
> 
> backup time, files (+sizes), last verification info (+link to task log), etc.

Yeah, that's what I basically meant first, show the whole info a
bit nicer, possibly even hide some columns of it by default then
(the list is quite cramped already)

> 
> or did you mean we add a new api endpoint that returns more info about the snapshot
> altogether? (which could also make sense)

I mean, then we'd not have to "shove" in the upload stats into the
generic list snapshots API call, as you wrote yourself, especially
if we never plan to show those inline it might make really more
sense to split that, even if we'd have the manifest already read
and thus in memory.

Without an in-depth analysis, I think I'd prefer that slightly
more, especially as the maintenance cost of that extra endpoint
should be rather negligible (if there's a good API endpoint path
to put it in, as that sometimes seems to be the harder part ^^)

And yes, we could then show all the possible data about a
snapshot, even if some of that is currently already included in
the content tree.




  reply	other threads:[~2023-11-27 10:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01  9:29 [pbs-devel] [RFC PATCH proxmox-backup 0/3] show upload statistics in gui Dominik Csapak
2023-08-01  9:29 ` [pbs-devel] [RFC PATCH proxmox-backup 1/3] api-types: make UploadStatistic an api type Dominik Csapak
2023-11-27  9:52   ` Thomas Lamprecht
2023-11-27 10:01     ` Dominik Csapak
2023-11-27 10:12       ` Thomas Lamprecht
2023-11-27 10:17         ` Dominik Csapak
2023-11-27 12:44           ` Wolfgang Bumiller
2023-11-27 14:57             ` Dominik Csapak
2023-08-01  9:29 ` [pbs-devel] [RFC PATCH proxmox-backup 2/3] api: datastore: add upload_statistic to snapshot listing Dominik Csapak
2023-11-27  9:08   ` Wolfgang Bumiller
2023-08-01  9:29 ` [pbs-devel] [PATCH proxmox-backup 3/3] ui: datastore content: add action to show upload statistics Dominik Csapak
2023-11-27  9:28   ` Thomas Lamprecht
2023-11-27 10:04     ` Dominik Csapak
2023-11-27 10:27       ` Thomas Lamprecht [this message]
2023-11-27 10:33         ` Dominik Csapak
2023-11-27 12:02           ` Thomas Lamprecht
2023-11-27 12:08             ` Dominik Csapak
2023-11-27 10:07     ` Thomas Lamprecht
2023-11-27 10:15       ` Dominik Csapak
2023-11-27 12:06         ` Thomas Lamprecht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=13828147-47a3-44dd-9bc3-0451038c2a56@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=d.csapak@proxmox.com \
    --cc=pbs-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal