[PATCH proxmox v5 02/42] notify: log which matchers matched on a notification

[Lukas Wagner <l.wagner@proxmox.com>]

This should make debugging notification issues much easier. Eventually,
this information shall also be recorded in a notification history, but
adding the log output is a valuable addition until then.

Suggested-by: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
Reviewed-by: Michael Köppl <m.koeppl@proxmox.com>
Tested-by: Michael Köppl <m.koeppl@proxmox.com>
---
 proxmox-notify/src/matcher.rs | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/proxmox-notify/src/matcher.rs b/proxmox-notify/src/matcher.rs
index 9964e4bf..cce86b6c 100644
--- a/proxmox-notify/src/matcher.rs
+++ b/proxmox-notify/src/matcher.rs
@@ -442,6 +442,7 @@ pub fn check_matches<'a>(
     notification: &Notification,
 ) -> HashSet<&'a str> {
     let mut targets = HashSet::new();
+    let mut matching_matchers = Vec::new();
 
     for matcher in matchers {
         if matcher.disable.unwrap_or_default() {
@@ -451,14 +452,27 @@ pub fn check_matches<'a>(
         }
 
         match matcher.matches(notification) {
-            Ok(t) => {
-                let t = t.unwrap_or_default();
+            Ok(Some(t)) => {
+                matching_matchers.push(matcher.name.clone());
                 targets.extend(t.iter().map(|s| s.as_str()));
             }
+            Ok(None) => {}
             Err(err) => error!("matcher '{matcher}' failed: {err}", matcher = matcher.name),
         }
     }
 
+    if !matching_matchers.is_empty() {
+        let target_list = Vec::from_iter(targets.clone());
+
+        info!(
+            "notification matched the following matchers: {}. The following targets will be notified: {}",
+            matching_matchers.join(", "),
+            target_list.join(", ")
+        );
+    } else {
+        info!("notification was not matched by any matcher");
+    }
+
     targets
 }
 
-- 
2.47.3