From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Constantin Herold <proxmox8914@herold.me>, pve-devel@lists.proxmox.com
Cc: Lukas Wagner <l.wagner@proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-manager 0/1] feat: pass backup status to hook script on job-end/job-abort
Date: Sat, 27 Sep 2025 14:33:15 +0200 [thread overview]
Message-ID: <004c09f5-a9fb-4866-80fa-063c7ed11f7c@proxmox.com> (raw)
In-Reply-To: <54300259-e13c-44c8-8382-872591d7bfcc@herold.me>
Am 27.09.25 um 13:13 schrieb Constantin Herold:
> So I wanted to migrate to the notification system now, but since you can't limit webhooks by type e.g. `backup result` it's not possible without another custom middleware service which would add unnecessary maintenance overhead and an additional point of failure.
You certainly can route only notifications from a backup job to a
notification target, simply create matcher with a filter that
has a type=vzdump rule for that.
Please check the documentation to get an overview about the quite
powerful notification system.
https://pve.proxmox.com/pve-docs/chapter-notifications.html
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-09-27 12:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250923174007.84121-1-proxmox8914@herold.me>
2025-09-23 17:40 ` [pve-devel] [PATCH pve-manager 1/1] " Constantin Herold via pve-devel
2025-09-24 9:40 ` [pve-devel] [PATCH pve-manager 0/1] " Thomas Lamprecht
2025-09-24 16:48 ` Constantin Herold via pve-devel
2025-09-27 11:13 ` Constantin Herold via pve-devel
[not found] ` <54300259-e13c-44c8-8382-872591d7bfcc@herold.me>
2025-09-27 12:33 ` Thomas Lamprecht [this message]
2025-09-23 17:40 Constantin Herold via pve-devel
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=004c09f5-a9fb-4866-80fa-063c7ed11f7c@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=l.wagner@proxmox.com \
--cc=proxmox8914@herold.me \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox