From: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
To: Lukas Wagner <l.wagner@proxmox.com>
Cc: pbs-devel@lists.proxmox.com, pve-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox 11/29] notify: matcher: add expression support
Date: Fri, 24 Jul 2026 08:59:36 +0200 [thread overview]
Message-ID: <uy3ag624mufb2dh7n2jocbj56bwp2aymckxoiybuhrwswrbmxr@5wxy4j5ie44u> (raw)
In-Reply-To: <20260709115716.299836-12-l.wagner@proxmox.com>
On Thu, Jul 09, 2026 at 01:56:58PM +0200, Lukas Wagner wrote:
> This commit adds support for the new 'expression' parameter in the
> matcher configuration. It contains a JSON-serialized match expression
> (based on the new proxmox-match-expression crate). It is intended as a
> replacement for the existing match-field, match-calendar,
> match-severity, mode and invert-match keys.
>
> The match expression implements a strict superset of the existing
> configuration keys, any existing configuration can be converted into
> an expression.
>
> Expressions lift some of limitations of the old approach, namely they
> allow arbitrary nesting of match rules and combinators.
>
> The following expressions are supported
> - all-of (corresponds to the former mode 'all')
> - any-of (corresponds to the former mode 'any')
> - one-of (new)
> - not (corresponds to former 'invert-match')
> - match-calendar (unchanged)
> - match-field (unchanged)
> - match-severity (unchanged)
>
> The combinators all-of, any-of and one-of support an arbitrary number of
> child expressions (where each child can be a combinator, not, or a
> match-* expression).
>
> Internally, existing, 'old-style' matchers are converted on the fly to
> expressions, meaning there is only a single code path for the matching
> logic. If any matcher has any of the old configuration keys and the new
> expression set, the old keys will be ignored and a warning will be
> logged.
>
> Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
one general thing i noticed while testing: it would be really useful to
know which matchers matched a notification. right now the only log
message you get is "notified via target {target}". such a change might
be a better fit in the notification history you have planned though.
another idea (bit more involved ^^): being able to construct test
notifications in the UI and showing a list of matching matchers.
(not particularly relevant to this specific patch, just thought about
this while reading it)
> ---
> Cargo.toml | 1 +
> proxmox-notify/Cargo.toml | 2 +
> proxmox-notify/src/matcher/expression.rs | 84 ++++++++++++++
> proxmox-notify/src/matcher/field.rs | 31 +++--
> proxmox-notify/src/matcher/mod.rs | 142 +++++++++++++----------
> proxmox-notify/src/matcher/severity.rs | 6 +-
> 6 files changed, 185 insertions(+), 81 deletions(-)
> create mode 100644 proxmox-notify/src/matcher/expression.rs
>
[...]
next prev parent reply other threads:[~2026-07-24 6:59 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 11:56 [PATCH many 00/29] notifications: add nested match expressions Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 01/29] add new proxmox-match-expression crate Lukas Wagner
2026-07-24 6:46 ` Arthur Bied-Charreton
2026-07-09 11:56 ` [PATCH proxmox 02/29] notify: promote matcher to dir-style module Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 03/29] notify: fix doc comment Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 04/29] notify: matcher: break out severity matcher into submodule Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 05/29] notify: matcher: break out field " Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 06/29] notify: matcher: break out calendar " Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 07/29] notify: matcher: calendar: add basic unit test Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 08/29] notify: matcher: add InlineSeverityMatcher Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 09/29] notify: matcher: add InlineFieldMatcher Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 10/29] notify: matcher: add InlineCalendarMatcher Lukas Wagner
2026-07-24 6:47 ` Arthur Bied-Charreton
2026-07-24 9:43 ` Wolfgang Bumiller
2026-07-09 11:56 ` [PATCH proxmox 11/29] notify: matcher: add expression support Lukas Wagner
2026-07-24 6:59 ` Arthur Bied-Charreton [this message]
2026-07-24 8:27 ` PVE::Cluster::cfs_lock_domain - bizarre issue Anthony Galica
2026-07-24 9:38 ` :Cluster::cfs_lock_domain " Anthony Galica
2026-07-25 7:14 ` Anthony Galica
2026-07-09 11:56 ` [PATCH proxmox 12/29] notify: api: support new expression parameter Lukas Wagner
2026-07-24 6:46 ` Arthur Bied-Charreton
2026-07-24 10:01 ` Wolfgang Bumiller
2026-07-24 11:38 ` Arthur Bied-Charreton
2026-07-09 11:57 ` [PATCH proxmox 13/29] notify: api: add `get_matcher_as_expression` Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox 14/29] notify: migrate PBS's and PVE's default matcher to expression syntax Lukas Wagner
2026-07-24 6:47 ` Arthur Bied-Charreton
2026-07-09 11:57 ` [PATCH proxmox 15/29] notify: move legacy matcher keys behind feature flag Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox-widget-toolkit 16/29] notification: increase matcher window width Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox-widget-toolkit 17/29] notifications: matcher: add support for match expressions Lukas Wagner
2026-07-24 6:45 ` Arthur Bied-Charreton
2026-07-09 11:57 ` [PATCH proxmox-widget-toolkit 18/29] notification: matcher: add better calendar editor Lukas Wagner
2026-07-24 6:46 ` Arthur Bied-Charreton
2026-07-09 11:57 ` [PATCH proxmox-widget-toolkit 19/29] notifications: matcher: consistently use title case for UI elements Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox-backup 20/29] notification: opt into 'legacy-matchers' feature in proxmox-notify Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox-backup 21/29] api: notification: add 'migrate-to-expression' parameter to get_matcher Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox-backup 22/29] ui: notification: enable new matcher UI Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox-perl-rs 23/29] notify: matcher: pass matcher config / updater directly Lukas Wagner
2026-07-28 13:09 ` Wolfgang Bumiller
2026-07-09 11:57 ` [PATCH proxmox-perl-rs 24/29] notify: opt into 'legacy-matchers' feature in proxmox-notify Lukas Wagner
2026-07-24 6:48 ` Arthur Bied-Charreton
2026-07-09 11:57 ` [PATCH proxmox-perl-rs 25/29] notify: add 'migrate_to_expression' parameter for get_matcher Lukas Wagner
2026-07-09 11:57 ` [PATCH manager 26/29] api: notification: pass config/updater directly to rust bindings Lukas Wagner
2026-07-31 7:19 ` Lukas Wagner
2026-07-09 11:57 ` [PATCH manager 27/29] api: notification: get_matcher: add 'migrate-to-expression' parameter Lukas Wagner
2026-07-09 11:57 ` [PATCH manager 28/29] api: notification: add 'expression' to matcher parameter schema Lukas Wagner
2026-07-09 11:57 ` [PATCH manager 29/29] ui: notification: enable new matcher UI Lukas Wagner
2026-07-24 6:44 ` [PATCH many 00/29] notifications: add nested match expressions Arthur Bied-Charreton
2026-07-24 6:53 ` Arthur Bied-Charreton
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=uy3ag624mufb2dh7n2jocbj56bwp2aymckxoiybuhrwswrbmxr@5wxy4j5ie44u \
--to=a.bied-charreton@proxmox.com \
--cc=l.wagner@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=pve-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 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.