GoogleUpdaterService alerts

[tarm]

I had this same issue and believe I resolved it using an Override in the Windows service discovery rule:



We can use regex here, so can create a filter rule for any service that contains GoogleUpdater:


Then in the condition, we can get the object we want the override to apply to, which in this case can be item prototype. Just need to state which item prototype to apply to using the condition, then override the Discover option and set to No:


So when the discovery rule runs, it will evaluate against the Override and should not create an item for any service containing GoogleUpdater. You could also override the Create enabled option and set that to No as well, just as an extra catch, however it's probably not required.

You could also do the same theory but against a Trigger prototype, in the case where you do want the item to be discovered and collect the data but don't want the alerts to be enabled etc.

Seems to be working for me so far. Hope this helps!

Thank's for your help. I will try it.

update: Unfortunatelly, it does not work for me (Zabbix 6.4.14)

[Buozinis]

Thank's for your help. I will try it.

update: Unfortunatelly, it does not work for me (Zabbix 6.4.14)

I was so happy to see MrB explanation, but it does not work

[[email protected]]

Works for me... You have to remove all references to discovered GoogleUpdater services then all problems will disappear. The Override blocks new GoogleUpdater discoveries but will not remove existing entries.

[CLSystems]

MrB explanations works for me, after removing the dot in the regex, so I use : ^GoogleUpdater*$ which works like a charm

[Staman]

Doesn't works for us either, zabbix 5.0.41
@msz@kommunekredit-dk: We removed all references to GoogleUpdater services and also cleared the dashboard notification.. still returned the errors after a while
@CLSystems: also tried to remove the "." in the expression .. no go

Please, any other suggestions? Could it be related to 5.x ? Or are here another people that it doesn't work for them ?
Thank you

[wunderwood]

My solution for the google updater service is to make it a manual service. We run it once a month during PM and reset it to a manual service. The google services we have running on our servers are not mission critical, and really should only be used during a PM anyway. No one should ever be surfing on Chrome from our servers. We are a small shop, so only a dozen Windows servers would have this issue. I will let you know if in a months time after the next PM if it continues to work.

[Ma33x]

Zabbix 7.0+
Templates -> Windows by Zabbix agent -> Macros -> {$SERVICE.NAME.NOT_MATCHES} -> add |^GoogleUpdater.*$| -> after that, delete the template from your host with a complete cleanup, save it, and add it again.

[PhilH]

Hello,
playing directly in the DB is quite more efficient and easy :
First, find what you want to hide :

SELECT * FROM zabbix.triggers WHERE description like '%GoogleUpdater%';

Then, modify status = 1 to disable the trigger :

UPDATE zabbix.triggers SET status = 1 WHERE description like '%GoogleUpdater%';

[cyber]

Hello,
playing directly in the DB is quite more efficient and easy :
First, find what you want to hide :

SELECT * FROM zabbix.triggers WHERE description like '%GoogleUpdater%';

Then, modify status = 1 to disable the trigger :

UPDATE zabbix.triggers SET status = 1 WHERE description like '%GoogleUpdater%';

You can do it in configuration->hosts-> triggers and then modifying the filter to


No need to mess around in DB...

[cyber]

Thats the place... mods in template will affect all hosts, where it is installed.

[musat-ccsd93]

I had this same issue and believe I resolved it using an Override in the Windows service discovery rule:

We can use regex here, so can create a filter rule for any service that contains GoogleUpdater:

Then in the condition, we can get the object we want the override to apply to, which in this case can be item prototype. Just need to state which item prototype to apply to using the condition, then override the Discover option and set to No:

So when the discovery rule runs, it will evaluate against the Override and should not create an item for any service containing GoogleUpdater. You could also override the Create enabled option and set that to No as well, just as an extra catch, however it's probably not required.
You could also do the same theory but against a Trigger prototype, in the case where you do want the item to be discovered and collect the data but don't want the alerts to be enabled etc.

Thank you. This resolved the issue, and set it up so that it doesn't come back. And I was able to use the suggestion to add an Override that disables the Trigger for the BITS service. Which seems to be a service that stops and starts regularly. Disabling the Trigger allows Zabbix to keep gathering the data, while not alerting me everything the service stops for a bit.

[fperaza]

How do I get to that configuration? I'm relatively new to Zabbix and I'm having exactly that problem

[cheneric]

Zabbix 7.0+
Templates -> Windows by Zabbix agent -> Macros -> {$SERVICE.NAME.NOT_MATCHES} -> add |^GoogleUpdater.*$|

Thanks for Ma33x.Work for me, Zabbix 7.2.5
Modifying the Templates will automatically apply.