Feature Request: Alarm Arguments Improvement

[mdigardford]

We like to run scripts when certain alarms error, one of them is the Backup Repo Free space one.


It would be great if the VBR that the repository is erroring on is included in one of these parameters, or another one is added, i think you can go up to 9 with the cmd prompt.

These are the arguments Veeam One passes in for this alarm.
%1 Custom - of Backup repository free space
%2 AHO Backup Repo
%3 Amount of free space (19.9%) is below a defined threshold (20.0%). Current free space is 3049.73 GB.
%4 1/27/2023 2:17:43 PM
%5 Warning
%6 Reset/resolved
%7 101

[mdigardford]

We like to run scripts on the when the agent backup job state alarm errors. It would be great if source node itself(ito082171) had its own argument, or the job and the node had there own argument instead of having to regex into the alarm summary.


%1 Custom - of Agent backup job state
%2 ito095626.hosts.cloud.ford.com
%3 Job "SQL Agent Backup EDC2H1 40 - ito082171.hosts.cloud.ford.com" finished with error Job finished with error at 1/24/2023 2:30:46 PM Processing finished with errors at 1/24/2023
2:30:46 PM Error: bad allocation Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: bad allocation Unable to retrieve next block
transmission command. Number of already processed blocks: [49]. Failed to download disk '9f57d809-8e41-460c-9b01-771a8b3197fe'. backups (G:) (50.0 GB)
%4 1/24/2023 2:32:19 PM
%5 Error
%6 Reset/resolved
%7116

[RomanK]

Hello Markus,

I've merged both topics into one, as they are similar from the development perspective.

In general, what you are requesting is doable but I cannot promise or provide any ETA. Could you please share your use case in detail, maybe we could find a workaround instead.

Thanks