Utilization of discoverer processes over 75% Problem won't clear

[techmattr]

Zabbix 7.2.5 Docker on Ubuntu
I've had this Utilization of discoverer processes over 75% problem in my Zabbix server host for 12 days now. I've disabled all of the discovery jobs and restarted the Zabbix container. I'm not sure why it still thinks there is a problem?

[kyus]

I was comparing Zabbix 6.0 to Zabbix 7.0 and it seems like the "discoverer data collector" process was removed and "discovery manager" and "discovery worker" internal processes were added in i'ts place.
Most likely, you did the upgrade to the newer version but the "Zabbix server health" template is still the same from the previous version. So the item isn't supported because this process doesn't exist in the newer releases.

I guess you can just update your template and the item and trigger will be removed.

[kyus]

Have you checked if the utilization of the discoverer processes went down after you disabled those discovery jobs?

[techmattr]

I think so. The only place I know to check this is the Zabbix health dashboard. The spikes are the history cleanup according to the periodic alerts we got on that process. But it doesn't looks like anything is just stuck above the threshold.

[kyus]

I guess you could try to manually close the problem (you may need to edit the trigger to be able to do it) to see if it will open again.
Besides the dashboard, you can check the latest data for this item.

[techmattr]

I wasn't able to find any way to edit or clear the trigger manually. It won't allow me to edit any part of it. It's all greyed out. I also noticed this error on the item. Invalid second parameter. I'm guessing this is why the trigger may be broken? Any idea how I would fix that Invalid second parameter? If I try to test the item I also get Invalid second parameter. The latest data for the item is blank as it also just has that Invalid second parameter.


item: I'm guessing the second parameter is the discoverer portion of the key? I can't figure out why that would be invalid.

[kyus]

I was comparing Zabbix 6.0 to Zabbix 7.0 and it seems like the "discoverer data collector" process was removed and "discovery manager" and "discovery worker" internal processes were added in i'ts place.
Most likely, you did the upgrade to the newer version but the "Zabbix server health" template is still the same from the previous version. So the item isn't supported because this process doesn't exist in the newer releases.

I guess you can just update your template and the item and trigger will be removed.

[kyus]

Oh, just an addition, you couldn't edit the trigger because it is from a template. You would need to edit it on the template, not directly in the host.

[techmattr]

Good call that is exactly what happened. Thank you!