Ad Widget

Collapse

Zabbix database full after adding Cisco Switch monitoring

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • doum
    Member
    • Oct 2019
    • 35

    #1

    Zabbix database full after adding Cisco Switch monitoring

    Hi,

    last week I have added all our Cisco switch in zabbix (template cisco snmp). (Less or more 300 switches)
    In 3 days, my postgresql database has grown to fill the 60Gb of disk space on the server...

    Is it normal ? I know a lot of informations are get by the template, but 60GB in 3 days....

    what can I do now ?

    thanks for your help
  • kloczek
    Senior Member
    • Jun 2006
    • 1771

    #2
    You can rethink what you need to monitor about your switches activity or you need to recalculate your storage resources needs.
    Lets say that you will be keeping raw history data for about 2 weeks so you will need to have 5 times more storage.
    To keep trends data for about 3 years you need to add another 5-7% on top of above quote.
    Actually to be able to maintain database content in long term you should have about two times more.
    http://uk.linkedin.com/pub/tomasz-k%...zko/6/940/430/
    https://kloczek.wordpress.com/
    zapish - Zabbix API SHell binding https://github.com/kloczek/zapish
    My zabbix templates https://github.com/kloczek/zabbix-templates

    Comment

    • doum
      Member
      • Oct 2019
      • 35

      #3
      Originally posted by kloczek
      You can rethink what you need to monitor about your switches activity or you need to recalculate your storage resources needs.
      Lets say that you will be keeping raw history data for about 2 weeks so you will need to have 5 times more storage.
      To keep trends data for about 3 years you need to add another 5-7% on top of above quote.
      Actually to be able to maintain database content in long term you should have about two times more.
      I have added more storage
      If I understand well, what is big is raw history, so after the data will stop growing as much

      Comment

      • kloczek
        Senior Member
        • Jun 2006
        • 1771

        #4
        Originally posted by doum

        I have added more storage
        If I understand well, what is big is raw history, so after the data will stop growing as much
        That really depends of how you will be maintaining content of the (mainly) history* tables.
        As long as you just started monitoring you should apply partitioning of history* and trends* tables to be able to delete oldest data using drop partition on SQL engine level.
        If you will be using default delete query database files will be only growing (and that is normal as well).
        With that volume of the data flowing over zabbix server you should have partitioned history* tables on daily bases and trends* tables using 4 weeks (~month) period.

        Other thing is that if you are using zabbix >= 4.2 you can reduce size of the data which will be written to the database by use on some items "discard unchanged" filter.
        I'm going to commit to set of my MIB based templates probably in 2-4 days
        Zabbix templates. Contribute to kloczek/zabbix-templates development by creating an account on GitHub.

        Here is short instruction about how to use that templates https://github.com/kloczek/zabbix-te...SNMP%20Devices
        http://uk.linkedin.com/pub/tomasz-k%...zko/6/940/430/
        https://kloczek.wordpress.com/
        zapish - Zabbix API SHell binding https://github.com/kloczek/zapish
        My zabbix templates https://github.com/kloczek/zabbix-templates

        Comment

        Working...