Zabbix history syncer processes more than 75% busy - How do I resolve this alert?

[jornell]

Hello, Some time ago I got the following alert "Zabbix history syncer processes more than 75% busy".

This alert appears when I try to navigate between my dashboards and makes them load forever. I attached pictures for clarity.

Zabbix Version: 6.0.19
BD: MariaDB
S.O: Ubuntu 20





If anyone knows why this alert appears and how to fix it, I would greatly appreciate it.

[MRedbourne]

These look like spikes. Is there anything happening around those times (large changes in nvps, large amounts of problems being generated, etc)?

On the Zabbix Server(s) open /etc/zabbix/zabbix_server.conf in your favourite text editor. Around line 250, there should be a section called "StartHistoryPollers" that's probably commented out. By default 5 history pollers are started on the Zabbix server. I would replace the line "# StartHistoryPollers=5" with "StartPollerHistory=10". (You're going to have to play with these numbers a little.) Rinse and repeat with:

"# StartTimers=1" -> "StartTimers=2"
"# StartEscalators=1" -> "StartEscalators=2"

I can't find the housekeeper forks though, I'm not sure they exist. Are there any errors in /var/log/zabbix_server.log?

[jornell]

Hello,

Those peaks are when I navigate between dashboards and change the time interval, which is when the alert is generated and the zabbix freezes.

Current configuration:


Also, I can't find information about "StartPollerHistory" in the configuration file and in the log /var/log/zabbix/zabbix_server.log I only find errors like:

"Failed: cannot extract value from json by path "$[?(@.Name == "1")].PercentDiskTime.first()": no data matches the specified path
1752:20230803:234022.671 error reason for "SERVER:vfs.dev.write.rate[DiskWritesPersec.1]" changed: Preprocessing failed for: [{"AvgDiskBytesPerRead":"0","AvgDiskBytesPerTran sfe r":"297642 ","AvgDiskBytesPerWrite":"297642","A..."

Thank you very much in advance.

[cyber]

Fix your DB and add primary keys... your screenshot show red "No" for those... It will speed up db usage. https://www.zabbix.com/documentation...0#primary-keys

Suggested "StartHistoryPollers" change is irrelevant, as those are used for calculated checks. It does not affect history sync. Same with timers and escalators, not used for history sync...

[jornell]

Sorry, I'm new to this, what do you mean by "Fix your DB" and adding this primary keys will affect the production environment? my zabbix database currently weighs approx 87GB

[cyber]

Did you read the link? there are further links to pages depending on your DB type... if it seems like klingon, then ask you friendly DBA to explain...