Job ID wont show up in notification rules

[SkyZoThreaD]

Hello,

I'm trying to use different notification rules to send sync job emails to a different recipient.
So I added a new notification target with the other recipient and added a notification matcher.
The issue there is : i can not find the job ID of my sync job here. The only i have is an id I don't know...
I tried to filter sync jobs without distinction and it works, but I'll have multiple sync jobs to send to different emails... I have to filter by job ID.
Any clue ? Am I missing something ?




Thank you !

 

[Lukas Wagner]

Works fine on my end, I just double checked.

Could you provide me with the output of proxmox-backup-manager versions --verbose and the contents of /etc/proxmox-backup/sync.cfg ?

Do you see anything in the system logs when you open the matcher window and try to select the (non-existing) sync job?

Thanks!

 

[SkyZoThreaD]

Hi Lukas,

Sorry for the huge delay

proxmox-backup                      4.0.0         running kernel: 6.14.8-2-pve
proxmox-backup-server               4.0.15-1      running version: 4.0.12     
proxmox-kernel-helper               9.0.4                                     
proxmox-kernel-6.14.8-2-pve-signed  6.14.8-2                                 
proxmox-kernel-6.14                 6.14.11-3                                 
proxmox-kernel-6.8.12-13-pve-signed 6.8.12-13                                 
proxmox-kernel-6.8                  6.8.12-13                                 
proxmox-kernel-6.8.12-9-pve-signed  6.8.12-9                                 
proxmox-kernel-6.8.12-5-pve-signed  6.8.12-5                                 
proxmox-kernel-6.8.12-4-pve-signed  6.8.12-4                                 
ifupdown2                           3.3.0-1+pmx10                             
libjs-extjs                         7.0.0-5                                   
proxmox-backup-docs                 4.0.15-1                                 
proxmox-backup-client               4.0.15-1                                 
proxmox-mail-forward                1.0.2                                     
proxmox-mini-journalreader          1.6                                       
proxmox-offline-mirror-helper       0.7.2                                     
proxmox-widget-toolkit              5.0.6                                     
pve-xtermjs                         5.5.0-2                                   
smartmontools                       7.4-pve1                                 
zfsutils-linux                      2.3.4-pve1

sync: s-647b8fa4-c797
        encrypted-only false
        group-filter group:vm/1000
        group-filter group:vm/1001
        group-filter group:vm/1002
        group-filter group:vm/1003
        group-filter group:vm/1004
        ns damicloud
        owner root@pam
        remote PBS-REDACTED
        remote-ns 
        remote-store redacted
        remove-vanished false
        schedule 08:00
        store backups
        sync-direction push
        transfer-last 1
        verified-only false

I managed to bypass the issue putting the "real" jobid into /etc/proxmox-backup/notifications.cfg and it works...

I dont know what logs to look into, but if you tell me i could provide you with it.
Anyway, the same issue happens on my second PBS with an other job. It's strange I'm the only one to face this

 

[patrick-]

Hi @SkyZoThreaD, you absolutely are not the only person experiencing this!
I created an account on this forum just to respond to this issue.

@Lukas Wagner I can verify exactly as reported here, there absolutely is a problem with the Proxmox Backup Server UI which causes the Sync Job IDs not to show up in the Match Rules of a Notification Matcher.

As described above, when using Match Field=Job ID, the Value list is not populated with the Job IDs of sync jobs.
However, this is much more serious than just not providing an "auto-complete" field. That particular box will not accept any custom user input. It cannot be submitted with anything but a pre-populated value.

Therefore, it is currently impossible to create a notification matcher for a specific sync job.
And yet, editing the config file at /etc/proxmox-backup/notifications.cfg and forcing the sync job ID in there actually works successfully, bypasses the UI limitation and successfully runs the matcher when that sync job completes!

Therefore this is a bug and the fix is actually very easy. The Notification Matcher is already compatible with sync job IDs, it simply needs to populate them into the Value field. Prune job and Verify job IDs already appear there, but Sync job IDs do not.

It would be great if you could help report this bug/limitation to the team as the fix is very simple: add sync job IDs into the pre-populated value field list when matching on Job ID in the Notification Matcher.

Apart from editing the config file (which is a very poor workaround), there is simply no way to run a matcher for a specific sync job until this UI issue is fixed, which is a very valid way to check that a specific sync job succeeded.

Note: just updated and reproduced in latest proxmox-backup-server 4.1.0-1 running version: 4.1.0

Thanks

 

[Lukas Wagner]

Sorry for not following up on this original issue.

Therefore this is a bug and the fix is actually very easy. The Notification Matcher is already compatible with sync job IDs, it simply needs to populate them into the Value field. Prune job and Verify job IDs already appear there, but Sync job IDs do not.

It would be great if you could help report this bug/limitation to the team as the fix is very simple: add sync job IDs into the pre-populated value field list when matching on Job ID in the Notification Matcher.

Your proposed "very simple fix" is exactly what is implemented at the moment.

I finally managed to reproduce the issue, seems like it only happens for 'Push' jobs, for 'Pull' jobs (which were the only ones available when the notification stack was introduced), it seems to work fine.

Thankfully, it was a rather easy fix indeed:
https://lore.proxmox.com/pbs-devel/20251215132733.216592-1-l.wagner@proxmox.com/T/#u

 

[patrick-]

Amazing! Thank you so much for helping to fix this!

You're right, it was indeed a push sync job that I was trying to notify on.
This fix will be a big help in sync monitoring and alerting!

Thanks again