Ad Widget

Collapse

Zabbix-proxy and data arrival delay.

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • bashman
    Senior Member
    • Dec 2009
    • 432

    #16
    I have the same problem with zabbix_proxy.
    978 Hosts / 16.901 Items / 8.703 Triggers / 44 usr / 90,59 nvps / v1.8.15

    Comment

    • chivo
      Junior Member
      • Mar 2009
      • 11

      #17
      There are two possible or probable causes:

      Your proxy isn't sending data to your master server fast enough, or your mysql database isn't fast enough to take in all of the data.

      For your proxy, consider updating the DataSenderFrequency if you think the proxy isn't sending data fast enough:

      # How often will the proxy send data to the master
      # server in seconds
      # Default 10 (according to documentation)
      DataSenderFrequency=1

      If you are still experiencing lags, then look at your master server. Consider increasing the number of trappers from the default 5 to 10.

      Also, see this thread on mysql database performance tuning:



      Some problems I ran into initially included: the database tables are using the myisam db engine rather than innodb and unoptimized memory settings for mysql. It took a lot of trial and error to get mysql to perform optimally.

      Another thing that can bring your server to a halt is the zabbix house keeping. I run it just twice a day. The history and history_uint table can get really big, really fast.

      Speaking of history, DON'T KEEP IT FOR VERY LONG. Unless you have a specific need, such as for building reports, there is little reason to keep your item checks in history for more than 7 days. The zabbix graphing functionality uses the trends table primarily, using history to fill in the gap for the previous few days only.

      Those are just some of the common problems I've run into or have helped other people with. Search the manual, there are lots of interesting tidbits in there, though I would always ask the devs for more documents!

      Comment

      • bashman
        Senior Member
        • Dec 2009
        • 432

        #18
        Thanks chivo, it was a database performance problem, and now it's solved.

        Although I use the daemontools to raise zabbix_proxy just in case it dies:

        978 Hosts / 16.901 Items / 8.703 Triggers / 44 usr / 90,59 nvps / v1.8.15

        Comment

        Working...