public inbox for pdm-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Lukas Wagner" <l.wagner@proxmox.com>
To: "Stefan Hanreich" <s.hanreich@proxmox.com>,
	"Proxmox Datacenter Manager development discussion"
	<pdm-devel@lists.proxmox.com>,
	"Lukas Wagner" <l.wagner@proxmox.com>
Subject: Re: [pdm-devel] [PATCH datacenter-manager 0/4] system report via admin cli or API
Date: Mon, 01 Dec 2025 16:18:32 +0100	[thread overview]
Message-ID: <DEMZBBCK0HAJ.1G3K2DNBWRUJM@proxmox.com> (raw)
In-Reply-To: <df396355-5736-4fc5-ac9d-97210e0b34b9@proxmox.com>

On Mon Dec 1, 2025 at 4:05 PM CET, Stefan Hanreich wrote:
> Tested this on my machine, works fine!
> * used CLI to generate a report
> * used API to obtain a report
>
>
> Some thoughts on the report itself:
>
> * Add some more networking info? (potential personal bias)
>
> $ ip -details -statistics address
> $ ip -details -4 route show
> $ ip -details -6 route show
>
> Might be interesting to include them as well, some people might use e.g.
> wireguard or some other VPN solutions to connect to their PVE instances
> and those most likely won't show up just in the
> `/etc/network/interfaces`. Particularly when troubleshooting issues with
> connectivity to PVE routing information could be vital.
>
> * df command in PVE includes -T flag as well (shows type of mount)
>
> * order-wise I think it would be better to run the 'commands' section
> first (particular because of date and version info).
>
>
> Barring any additions, consider this:
> Tested-by: Stefan Hanreich <s.hanreich@proxmox.com>
>

Ack, I'll add these commands and then change the order; v2 incoming.

Thanks!


_______________________________________________
pdm-devel mailing list
pdm-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel


  reply	other threads:[~2025-12-01 15:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-01 12:58 Lukas Wagner
2025-12-01 12:58 ` [pdm-devel] [PATCH datacenter-manager 1/4] server: add system report implementation Lukas Wagner
2025-12-01 14:55   ` Shannon Sterz
2025-12-01 15:06     ` Lukas Wagner
2025-12-01 12:58 ` [pdm-devel] [PATCH datacenter-manager 2/4] api: add system report API Lukas Wagner
2025-12-01 12:58 ` [pdm-devel] [PATCH datacenter-manager 3/4] cli: admin: add 'report' command to generate a system report Lukas Wagner
2025-12-01 12:58 ` [pdm-devel] [PATCH datacenter-manager 4/4] pdm-client: add bindings for system report generation Lukas Wagner
2025-12-01 14:55 ` [pdm-devel] [PATCH datacenter-manager 0/4] system report via admin cli or API Shannon Sterz
2025-12-01 15:05 ` Stefan Hanreich
2025-12-01 15:18   ` Lukas Wagner [this message]
2025-12-01 15:34 ` [pdm-devel] superseded: " Lukas Wagner

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=DEMZBBCK0HAJ.1G3K2DNBWRUJM@proxmox.com \
    --to=l.wagner@proxmox.com \
    --cc=pdm-devel@lists.proxmox.com \
    --cc=s.hanreich@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