From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id C7D93C0467 for ; Wed, 10 Jan 2024 14:43:47 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id A8A2C34BDF for ; Wed, 10 Jan 2024 14:43:17 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Wed, 10 Jan 2024 14:43:17 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id D353849082 for ; Wed, 10 Jan 2024 14:43:16 +0100 (CET) Date: Wed, 10 Jan 2024 14:43:16 +0100 (CET) From: Christian Ebner To: Lukas Wagner , Proxmox VE development discussion Message-ID: <1593135089.2170.1704894196191@webmail.proxmox.com> In-Reply-To: <9a3474b0-3422-4bda-b669-f28067351008@proxmox.com> References: <20240110131431.125035-1-c.ebner@proxmox.com> <9a3474b0-3422-4bda-b669-f28067351008@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Priority: 3 Importance: Normal X-Mailer: Open-Xchange Mailer v7.10.6-Rev57 X-Originating-Client: open-xchange-appsuite X-SPAM-LEVEL: Spam detection results: 0 AWL 0.054 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 T_SCC_BODY_TEXT_LINE -0.01 - Subject: Re: [pve-devel] [PATCH pve-docs] notifications: fix typos and improve reading flow X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2024 13:43:47 -0000 > On 10.01.2024 14:37 CET Lukas Wagner wrote: > > > On 1/10/24 14:14, Christian Ebner wrote: > > Signed-off-by: Christian Ebner > > --- > > notifications.adoc | 10 +++++----- > > 1 file changed, 5 insertions(+), 5 deletions(-) > > > > diff --git a/notifications.adoc b/notifications.adoc > > index cddb8ca..9be23f8 100644 > > --- a/notifications.adoc > > +++ b/notifications.adoc > > @@ -172,11 +172,11 @@ Notification Matchers > > [thumbnail="screenshot/gui-datacenter-notification-matcher.png"] > > > > Notification matchers route notifications to notification targets based > > -on their matching rules. These rules can match of certain properties of > > -a notification, such as the timestamp (`match-calendar`), the severity of > > -the notificaiton (`match-severity`) or metadata fiels (`match-field`). > > -If a matcher matches a notification, all targets configured for the matcher > > -will receive the notification. > > +on their matching rules. These rules can match certain properties of a > > +notification, such as the timestamp (`match-calendar`), the severity of > > +the notificaiton (`match-severity`) or metadata fields (`match-field`). > ^ > Spotted another typo here Ah, yes, will send a v2. Thanks for noticing! > > > +If a notification is matched by a matcher, all targets configured for the > > +matcher will receive the notification. > > > > An arbitrary number of matchers can be created, each with with their own > > matching rules and targets to notify. > > I guess I wrote that paragraph in a bit of a hurry :) > > Thanks! No worries!