aholiveira

Hello, The supported job types by the current version are the ones defined in the script, variable `$typeNames` on line 88. If you know what job types those are you...

Hello @thmcon, Which version of the template are you using? I've had a few issues with that trigger: When using last(LastStart) I was having the trigger active right when the...

Hello @thmcon, Thank you for your input. Let's keep this under observation. One question: What is the {#JOBTYPEID} for the job you are having issues? You can check this on...

Hello again, This part of your condition will prevent the trigger to activate if the last two values of the job Progress are different (so it will almost never trigger)....

Hello @thmcon, On the installations I'm managing that expression gave "early triggers", activating the trigger at the start of the job for a few seconds. Did you not have any...

Hello, I've let this run again tonight without changing the trigger expression, and again, all backup jobs the trigger was active for a few seconds right at the start of...

Hello, Once a backup is finished (to completion) the progress is always 100 (zabbix will keep collecting that data even when the backup job is done). Also, bear in mind...

Hello, The latest version of Zabbix is 6.2. Versions 6.0 and 5.0 are still supported but I'd suggest upgrading (at least to the next LTS 6.0 version). The upgrade process...

Hello @thmcon, Thank you for your comments. 1 - That was one of the main reasons for proposing this, so that configuration could be done in a single place. This...

Hello @thmcon, The script is pulling information from the last job session from the database, which is why you are also seeing different information on Zabbix. I don't think we...