Proxy DB Size

[karanpreetsingh1990]

Hello,

I'm quite new to zabbix and still getting the hang of things and I've been facing an issue with the proxy database size.

We do have a large number of hosts/items reporting in to the proxy but the size seems to grow very large within a couple of weeks. The current size it around 700GB which seems very huge considering the proxy shouldn't be storing that much data.

The one table is particular is getting that large is "proxy_history".

Previously I had to delete the rows and optimize the table in mysql db to get the size back to normal but we can't keep doing that. Also, my understanding was that the housekeeper will go ahead and delete the history every hour or so. It shouldn't be growing that large if that was the case. I also noticed that the proxy configuration doesn't have a max housekeeper delete parameter that I could increase so that more rows get deleted. I'm not even sure if that's the issue though.

Is there a way I can control this size?

Also, I've been looking into partitioning the Server DB but from what I've understood the proxy DBs don't need partitioning but I'm now wondering if that would be something I should do.

About my setup:
RHEL7.7
Zabbix 4.4.7 with server, proxy and DB all on separate hosts
DB is mysql

Any help would be much appreciated!

Thanks,
Karan

[karanpreetsingh1990]

Hello,

I'm quite new to zabbix and still getting the hang of things and I've been facing an issue with the proxy database size.

We do have a large number of hosts/items reporting in to the proxy but the size seems to grow very large within a couple of weeks. The current size it around 700GB which seems very huge considering the proxy shouldn't be storing that much data.

The one table is particular is getting that large is "proxy_history".

Previously I had to delete the rows and optimize the table in mysql db to get the size back to normal but we can't keep doing that. Also, my understanding was that the housekeeper will go ahead and delete the history every hour or so. It shouldn't be growing that large if that was the case. I also noticed that the proxy configuration doesn't have a max housekeeper delete parameter that I could increase so that more rows get deleted. I'm not even sure if that's the issue though.

Is there a way I can control this size?

Also, I've been looking into partitioning the Server DB but from what I've understood the proxy DBs don't need partitioning but I'm now wondering if that would be something I should do.

About my setup:
RHEL7.7
Zabbix 4.4.7 with server, proxy and DB all on separate hosts
DB is mysql

Any help would be much appreciated!

Thanks,
Karan

This is still an issue. Any help would be great.

Thanks,
Karan

[aib]

Please, check "data_sender" process. It is the process which sending data from Proxy to main server and mark for delete records in local DB. If data_sender cannot send data to main server, data are sitting in local DB.
I assume that your proxy collecting so much data that it cannot be send to main DB before receiving new data.
Or your connection between local proxy and main server is very slow.

Check graph "Internal process busy" from template Zabbix Proxy.

[karanpreetsingh1990]

Please, check "data_sender" process. It is the process which sending data from Proxy to main server and mark for delete records in local DB. If data_sender cannot send data to main server, data are sitting in local DB.
I assume that your proxy collecting so much data that it cannot be send to main DB before receiving new data.
Or your connection between local proxy and main server is very slow.

Check graph "Internal process busy" from template Zabbix Proxy.

I checked the internal process busy in the graph but I see no data being reported for that.



If I check the server though and try to see the processes, I do see that the data sender is able to send the data.

/usr/sbin/zabbix_proxy: data sender [sent 396 values in 0.610063 sec, sending data]

Also, I am able to see the data on the UI showing up and alerts are being generated that I assume wouldn't happen if the server wasn't getting the data.

The size goes down when I optimize the table and almost returns back to it's original size.

Any thing else that could be causing this?

Regards,
Karan

[aib]

small dirty configuration trick: Zabbix Proxy must be monitored by themselves.
So check the configuration of host "Zabbix Proxy 001" and change settings for "Monitored by" to "Zabbix Proxy

[karanpreetsingh1990]

I made the change to the zabbix agent on the server and the Host configuration on the UI and can now see the details on the graph. Thanks a lot for that trick!!

I see that the Data Sender is around 50% utilized on average. Could this be causing the issues?



Also, How could I get that utilization down? Any settings on the Server side that could help me get this resolved?

Regards,
Karan

[karanpreetsingh1990]

Made some changes to the settings on both the server and proxy side and the data sender is now averaging around 30%. Will keep it running overnight and also note the DB size to see if it made much of a difference.

[lptarik]

How did you solve this issue?

[derli1988]

I'm using template Zabbix proxy health and some items are not being collected like Zabbix proxy: Utilization of data sender internal processes, in % with error No "data sender" processes started.

The proxy host is being monitored by itself