Exclude Multiple Jobs in Alarm Rules

[bg.ranken]

So I'm trying to exclude jobs from the "Suspicious incremental backup size" alarm. In the rules section there is a field for excluding jobs, however I've only been successful adding a single job. When typing the job it does show a drop down, but I want to do multiple jobs. I tried separating with a few common delimiters like commas or semicolons, but none of them seem to work.

How would you exclude multiple jobs from this alarm?

Also a side question, is there any way to exclude only specific VMs from this alarm?

[wishr]

Hi Randall,

Currently, you can only specify a single mask for this particular alarm and all jobs that fall under the selection will not cause the alarm to trigger. We'll try to improve it in future versions.

No, currently there is no way to exclude particular VMs from this alarm.

Thanks

[bg.ranken]

What do you mean a single mask?

[wishr]

It's a simple exclusion mask. E.g. if you specify "A*" all jobs having "A" in the beginning of their names will not cause the alarm to trigger, but in this particular alarm rule, you can only specify a single mask, not multiple.

[TWuser]

Definitely a +1 here for excluding specific VMs. Most of our jobs are fairly large and excluding all VMs is a bad idea, but getting spammed for a VM I know has high variability makes me want to turn the alarm off completely.

[jorgedlcruz]

Hello,
This is a very valid feedback, will discuss with the team and add it to the backlog for future releases.

Thanks a lot!

[kirderf]

I just wanted to upvote this.

Any update on when/if this feature will be available?

[tgicountry]

Would be nice to exclude multiple jobs. Suspicious incremental alarms are incredibly difficult to manage without more granularity in Include/Exclude.

[jorgedlcruz]

Thank you so much, feedback is noted. We can not share any specific date. We would try to include some improvements in future releases.

[kaffeine]

+1 for the ability to exclude backup jobs on specific alarms.

In our case it pertains multiple disabled jobs (that are set so intentionally), and we keep getting nagged by Veeam One about them.