Change in Trigger Prototype keeps the Old Trigger in the Item !!

[João Medeiros]

Hi,

Using Zabbix 3.4.8, in CentOS Linux release 7.4.1708 (Core)

By default, the windows template has some Discovery Rules.

For instance, Mounted filesystem discovery

1- I entered in Mounted filesystem discovery and Changed an Trigger Prototype

The Trigger Prototype was:
Free disk space is less than 20% on volume {#FSNAME}

I changed to:
Free disk space is less than 10% on volume {#FSNAME}

But I noticed that in MariaDb, in table triggers , it keeps the Old trigger, and I continue to receive alerts from that the Old trigger.

In some cases I used the command below to fix my problem:

MariaDB [zabbix]> delete from triggers where description LIKE '%disk%space%20%';

But in another cases I couldn't use that trick, because I receive errors from the database
ERROR 1451 (23000): Cannot delete or update a parent row: a foreign key constraint fails (`zabbix`.`trigger_discovery`, CONSTRAINT `c_trigger_discovery_2` FOREIGN KEY (`parent_triggerid`) REFERENCES `triggers` (`triggerid`))

(I know, it's not the best ideas to change directly in the database, but at this moment I don't know how using the zabbix console)

What am I doing wrong ?

Instead to change a trigger prototype, do I have to disable a Triger prototype and create another ?

I notice that if I change a Trigger Prototype to Create Enabled = No , aparently it doesn't create a new trigger in trigger table,
but it continues also using the Old trigger, sending alerts that I don't need.

Thanks

[kloczek]

Look on LLD item (not prototype) definition how frequently this item is updated and by this all populated items/triggers/graphs prototypes are populated/regenerated.

[João Medeiros]

Thank you --- I found this "For prototypes, you will need to clone the existing, make your update, add, then go back and delete the old. " Source - https://www.zabbix.com/forum/zabbix-...created-by-lld