Uploaded image for project: 'ZABBIX FEATURE REQUESTS'
  1. ZABBIX FEATURE REQUESTS
  2. ZBXNEXT-714

need scalable alternative for the history and items tables

    XMLWordPrintable

Details

    • Change Request
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 1.8.2
    • None
    • Server (S)
    • Linux, Postgresql

    Description

      We have hundreds of monitored servers with thousands of checks in total. The size of the items and various history tables in the Zabbix database is a major scalability problem for us – we've got it running on a very fast RAID array with 10+ disks, but a postgres autovacuum of the items table makes the server almost unusable.

      Long-term the amount of data we can store in those tables will limit whether we can continue to use Zabbix. Has any thought been given to a more scalable storage mechanism? Some ideas:

      • partition the tables in SQL (we'd be OK with switching to mySQL if needed, but some official support for table partitioning could help)
      • support storing the huge data in BerkeleyDB, Cassandra, Hadoop, or some other more scalable storage mechanism

      Attachments

        Issue Links

          causes

          New Feature Request - A new feature request of the product, which has yet to be developed. ZBXNEXT-4417 Real time value, trends, events export module (Z4)

          • Major - Major loss of function.
          • Closed

          New Feature Request - A new feature request of the product, which has yet to be developed. ZBXNEXT-4868 Support of TimescaleDB

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Closed
          depends on

          New Feature Request - A new feature request of the product, which has yet to be developed. ZBXNEXT-3661 Support of RestAPI or JSON RPC as back-end transport for history database

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Reopened
          is duplicated by

          New Feature Request - A new feature request of the product, which has yet to be developed. ZBXNEXT-2640 Add ability to send numeric history to amqp queue for distribution to other databases

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Reopened

          New Feature Request - A new feature request of the product, which has yet to be developed. ZBXNEXT-2810 Send data to Fluentd

          • Major - Major loss of function.
          • Closed

          New Feature Request - A new feature request of the product, which has yet to be developed. ZBXNEXT-1836 Support of loadable modules for alternative storage of historical data

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Closed
          part of

          New Feature Request - A new feature request of the product, which has yet to be developed. ZBXNEXT-4417 Real time value, trends, events export module (Z4)

          • Major - Major loss of function.
          • Closed

          Activity

            People

              alexei Alexei Vladishev
              harpo Will Lowe
              Votes:
              85 Vote for this issue
              Watchers:
              76 Start watching this issue

              Dates

                Created:
                Updated: