Werk 16430 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # veeam_jobs: Always Monitor Result of Last Backup key | value ---------- | --- date | 2024-06-05T14:36:09+00:00 version | 2.3.0p6 class | fix edition | cee component | checks level | 1 compatible | yes Previously, the check plugin `veeam_jobs` would not always check the result of the last backup job to determine the monitoring state. If the creation time was an empty string, it would show `item not found`. Moreover, if the last state of the plugin was `Starting`, `Working` or `Postprocessing`, then the check would be OK, even if the last backup failed. The check now shows all the information available unconditionally. Moreover, * a Success result is OK, * a Warning result is WARN, * a Failed result is CRIT, * a None result is OK or UNKNOWN. There is no change in behaviour in this case. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # veeam_jobs: Always Monitor Result of Last Backup key | value ---------- | --- date | 2024-06-05T14:36:09+00:00 version | 2.3.0p6 class | fix edition | cee component | checks level | 1 compatible | yes Previously, the check plugin `veeam_jobs` would not always check the result of the last backup job to determine the monitoring state. If the creation time was - an empty string, it would show `item not found` in case. It will now show all - the information available and the correct monitoring state. + an empty string, it would show `item not found`. Moreover, if the last + state of the plugin was `Starting`, `Working` or `Postprocessing`, then the + check would be OK, even if the last backup failed. + The check now shows all the information available unconditionally. Moreover, + * a Success result is OK, + * a Warning result is WARN, + * a Failed result is CRIT, + * a None result is OK or UNKNOWN. There is no change in behaviour in this case. +