Change trigger value for particular LLD discovered item

[onallion]

Hey guys,

Is there any way to change a trigger value for a particular item that was discovered using LLD?

For example I have several datastores, and a trigger that warns when read/write latency goes over 30ms. What if I want a particular datastore to have a higher threshold? I can't seem to find any way to do this. Help would be appreciated

[batchenr]

Hey guys,

Is there any way to change a trigger value for a particular item that was discovered using LLD?

For example I have several datastores, and a trigger that warns when read/write latency goes over 30ms. What if I want a particular datastore to have a higher threshold? I can't seem to find any way to do this. Help would be appreciated

you can manually change it.
go to host-triggers-click on triggers name- and then press on its name again
and change the values.

make sure trigger values start with the server name and not template name so you wont change to everybody.

[onallion]

But then I have to do this for every single host that has this datastore. Is there any way to make it more general, like use a macro for host name in the template?

Basically I DO want to change it to everybody, but it seems I can't use template name instead of host names when referring to a specific item, so this doesn't work:

{Template Virt VMware Hypervisor:vmware.hv.datastore.read[{$URL},{HOST.HOST},PROBELM_DATASTORE,latency].min(10m)}>200

[batchenr]

But then I have to do this for every single host that has this datastore. Is there any way to make it more general, like use a macro for host name in the template?

Basically I DO want to change it to everybody, but it seems I can't use template name instead of host names when referring to a specific item, so this doesn't work:

{Template Virt VMware Hypervisor:vmware.hv.datastore.read[{$URL},{HOST.HOST},PROBELM_DATASTORE,latency].min(10m)}>200

if you want to change it to everybody just change it at the template
no need to change template name only the values min(10m)}>200

[onallion]

I want to change it for all HOSTS that are using that template, but only for a particular datastore (that they all share). That is my problem

[batchenr]

I want to change it for all HOSTS that are using that template, but only for a particular datastore (that they all share). That is my problem

now i get you.
so what i think
1. change them one by one manually
2. create a script with zabbix_sender that will make this specific quary and add it
to a template and add this template to all this host- but in anyways you will have to go one by one to disable the current check.

but im no expert.

[mobarrio]

you can manually change it.
go to host-triggers-click on triggers name- and then press on its name again
and change the values.

make sure trigger values start with the server name and not template name so you wont change to everybody.

Hi batchenr,
I have the same problem with LLD. I try change a single trigger like you say in the post but my trigger are read only, what I do wrong?

We use the default "Template Virt VMware Guest" and try personalize some triggers but I don't know how.

Any suggest?





Brgds,

Mariano

[piandao]

Hi batchenr,
I have the same problem with LLD. I try change a single trigger like you say in the post but my trigger are read only, what I do wrong?

We use the default "Template Virt VMware Guest" and try personalize some triggers but I don't know how.

Any suggest?





Brgds,

Mariano

Hey mobarrio, did you ever figure out how to edit read-only triggers?
Or do I have to go back through the dependent triggers until I find one that can be edited? I don't really want to do it like that as it'll affect all the hosts using that template/discovery rule instead of this one specific host.

[aib]

Maybe I say trivia things or sound complicated but did you ever think about creating second discovery rule with DIFFERENT filter expression and change trigger prototype to fulfill your needs?
Like that for template "Template Virt VMware Guest":
1) First Discovery rule for Disk device discovery have a filter expression "General datastore" with some preconfigured names for datastores and trigger prototype for latency >20
2) Second Discovery rule for Disk device discovery have a filter expression "SLOW datastore" with some preconfigured names (must not exist in datastore name) and trigger prototype for latency >200

Just from the top of my head.

Useful links :
https://www.zabbix.com/documentation...ar_expressions (regular expressions)
https://www.zabbix.com/documentation...ed_filesystems (discovery of filesystems)

[piandao]

Yeah I ended up doing something similar right after I posted.
I cloned the existing trigger, changed the expression of this new trigger to suit my needs and disabled the original read-only trigger.