Notification matcher not matching on job-id

[srs]

Trying to create a notification matcher that will match on a backup job but its not working.

If I remove the match field: job-id then the matcher works, so it's not matching the job-id.

I have another system where the same rules work fine!

 

[Lukas Wagner]

How is the backup triggered? By schedule or by the 'Run now' button? To quote from the docs [1]:

Backup job notifications only have job-id set if the backup job was executed automatically based on its schedule, but not if it was triggered manually by the Run now button in the UI.

This is due to a technical limitation with regards how the 'Run now' button is implemented, I hope we can resolve this at some point in the future.

[1] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#notification_events

 

[srs]

Thank you, yes I was triggering it manually while testing, but the initial failure was for the scheduled task.

The scheduled task was returning a "Error: unexpected status" so I think the notifications were not working.

I have modified my postfix configuration and hopefully fixed it.

 

[Arpxqq]

How is the backup triggered? By schedule or by the 'Run now' button? To quote from the docs [1]:



This is due to a technical limitation with regards how the 'Run now' button is implemented, I hope we can resolve this at some point in the future.

[1] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#notification_events

Good afternoon

That's exactly what was my downfall today. I was very sure that the rules were set correctly by the matcher, but I didn't get a message when the task was triggered manually for a test!

It only works if the task is started automatically by the system

It's not a huge problem, but it's annoying until you figure it out.

I think it will take a while for this to work as this shouldn't be a high priority

Greetings

Arp