From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9])
	by lore.proxmox.com (Postfix) with ESMTPS id D52D31FF56B
	for <inbox@lore.proxmox.com>; Mon, 22 Apr 2024 11:15:10 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
	by firstgate.proxmox.com (Proxmox) with ESMTP id 71971CDAA;
	Mon, 22 Apr 2024 11:15:13 +0200 (CEST)
Message-ID: <56c3600e-8def-4f3d-a1f8-684daffbf98a@proxmox.com>
Date: Mon, 22 Apr 2024 11:15:08 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Fiona Ebner <f.ebner@proxmox.com>,
 Proxmox VE development discussion <pve-devel@lists.proxmox.com>
References: <20240422083116.99809-1-l.wagner@proxmox.com>
 <20240422083116.99809-16-l.wagner@proxmox.com>
 <f6c6d882-a3cf-4a60-ab0d-3fdd8d000cef@proxmox.com>
Content-Language: de-AT, en-US
From: Lukas Wagner <l.wagner@proxmox.com>
In-Reply-To: <f6c6d882-a3cf-4a60-ab0d-3fdd8d000cef@proxmox.com>
X-SPAM-LEVEL: Spam detection results:  0
 AWL 0.001 Adjusted score from AWL reputation of From: address
 BAYES_00                 -1.9 Bayes spam probability is 0 to 1%
 DMARC_MISSING             0.1 Missing DMARC policy
 KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
 SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
 SPF_PASS               -0.001 SPF: sender matches SPF record
Subject: Re: [pve-devel] [PATCH docs v6 15/16] notifications: describe new
 notification metadata fields
X-BeenThere: pve-devel@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: pve-devel-bounces@lists.proxmox.com
Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com>



On  2024-04-22 11:10, Fiona Ebner wrote:
>> +| Cluster node fenced              |`fencing`          | `error`  | `hostname`
>> +| Storage replication job failed   |`replication`      | `error`  | `hostname`, `job-id`
>> +| Backup succeeded                 |`vzdump`           | `info`   | `hostname`, `job-id` (only for backup jobs)
>> +| Backup failed                    |`vzdump`           | `error`  | `hostname`, `job-id` (only for backup jobs)
> 
> I think the "(only for backup jobs)" should not be there, or?
> 

No, that should be there. The `job-id` field is set if the backup is started
as a scheduled job and if that job is started by hand, but *not* if
e.g. a single VM is backed up manually. Would not make sense for the latter,
since that one has no associated job.

-- 
- Lukas


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