Zabbix discoverer processes more than 75% busy, zabbixdiscoverer

Zabbix discoverer processes more than 75% busy, zabbixdiscoverer

Originally published in cu:

Cause and solution of Zabbix discoverer processes more than 75% busy.

I. symptom

After the discovery task is configured, The zabbix dashboard generates the following alarms:

Zabbix discoverer processes more than 75% busy

Ii. Cause

1. Each configuration of a discovery task occupies one discovery process within a certain period of time, and zabbix_server.conf has only one discovery by default (commented, effective by default );

2. In order to quickly verify the automatic detection effect, set the "Delay" time of the discovery task from the default 3600s to 60 s.

Conclusion: There are two reasons why the discovery processes is too high on average and an alarm is reported.

Iii. Solution

1. modify the number of discovery processes in zabbix_server.conf;

# StartDiscoverers can be set based on the number of specified discovery tasks. The value range is 0 ~ 250 [root @ localhost ~] # Sed-I's | # StartDiscoverers = 1 | StartDiscoverers = 2 | G'/usr/local/zabbix/etc/zabbix_server.conf [root @ localhost ~] # Service zabbix_server restart

2. Set the "Delay" time of the discovery task to be long enough to reduce the process usage in the average time.

Iv. Results

In method 1, the usage of discovery processes is reduced to 50%, as shown below: