From: Rovshan Pashayev via pve-devel <pve-devel@lists.proxmox.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Cc: Rovshan Pashayev <Rovshan.Pashayev@veeam.com>
Subject: [pve-devel] Feature Request: Enhancing Error Messaging
Date: Tue, 2 Jul 2024 10:50:09 +0000 [thread overview]
Message-ID: <mailman.210.1719917786.331.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 11595 bytes --]
From: Rovshan Pashayev <Rovshan.Pashayev@veeam.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Subject: Feature Request: Enhancing Error Messaging
Date: Tue, 2 Jul 2024 10:50:09 +0000
Message-ID: <PH0PR14MB4735E67E7B94811CBBB3CCDB9FDC2@PH0PR14MB4735.namprd14.prod.outlook.com>
Dear Proxmox VE Team,
We kindly request the implementation of enhanced error messaging. Currently, all errors and failures are combined into a single string, making it difficult to identify and address specific issues.
Please consider introducing error codes or a similar mechanism to provide a structured format for error reporting. This would improve the user experience and expedite troubleshooting during third-party backup processes.
Thank you for your attention
Best regards,
Rovshan Pashayev, Analyst, Veeam Agent for Linux, Mac, AIX & Solaris
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2024-07-02 10:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 10:50 Rovshan Pashayev via pve-devel [this message]
2024-07-02 12:19 ` Fabian Grünbichler
2024-07-02 13:02 ` Rovshan Pashayev via pve-devel
[not found] ` <PH0PR14MB473525099909EC233147C0759FDC2@PH0PR14MB4735.namprd14.prod.outlook.com>
2024-07-02 13:22 ` Fabian Grünbichler
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=mailman.210.1719917786.331.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=Rovshan.Pashayev@veeam.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.