ZABBIX Forums  
  #1  
Old 03-08-2017, 20:12
clarkritchie clarkritchie is offline
Member
 
Join Date: Aug 2013
Posts: 44
Default Managing proxy_history table size

Hi all,

We have 3 proxies in a data center that has high latency to our Zabbix server (2.4). We are around 2,600 NVPS right now. We are using a proxy (3.2) which I've recompiled with ZBX_MAX_HRECORDS=2500 (default=1000).

Due to upstream outages, etc., its not uncommon for the one or more of the proxies to fall behind. Sometimes they recover, sometimes not. We've noticed the proxy_history table sometimes grows very large.

We currently run the default housekeeper setting on the proxy, however I'm thinking about disabling that and going with a partitioning strategy on proxy_history to better manage size, i.e. partitioning by day and only keeping maybe 3 days of history.

Question 1 -- What criteria does the housekeeper use to determine "old" data? Or am I missing where this can be defined? Is "old" an hour, a day, a week, a month?

Question 2 -- Is it safe to mess with the proxy_history table? The mysql partitioning howto doc seems to suggest that Zabbix is tolerant of this.

Thanks in advance.

Last edited by clarkritchie; 03-08-2017 at 20:14.
Reply With Quote
  #2  
Old 04-08-2017, 00:44
clarkritchie clarkritchie is offline
Member
 
Join Date: Aug 2013
Posts: 44
Default

I think I've answered my 2nd question. I partitioned the proxy_history table by hour, keeping 3 hours worth of data seems to work OK. Many thanks to whoever wrote the MySQL partitioning HOWTO, was an easy tweak to add hour-level partitioning to the day/month in the doc.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +2. The time now is 10:14.