Ad Widget

Collapse

hardware requirements for 110k parameters collection per minute

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • strikingsurface
    Junior Member
    • Nov 2024
    • 1

    #1

    hardware requirements for 110k parameters collection per minute

    Hello Community!

    hope you're well.

    I'm evaluating new network monitorign solution in my company, and one of candidates for this is obviously Zabbix.

    we have done some very initial checks of functionalities vs our requirements, so we would like to check what would be hardware requirements for our deployment.

    our setup is like this:
    - 2 DCs
    - 4500 network devices monitored (total).
    - current tool polls 110K metrics per minute (SNMP)
    - 2K of total device number are cisco switches/routers which have extra data polling via Cisco DNA API
    +
    as addon (we do not at the moment) we would like to directly monitor 5k AP with Ping + few SNMP metrics (we do monitor via WLCs but it has some drawbacks)

    we have data pollers/collectors configured with 2 clusters (1 per DC).
    if single DC VMs are shut down, then other is to handle all the monitoring load.

    in regards of DB - according to company requirements we have to use company provided postgres, so no need to handle this load..


    Could you please advise how many core per DC and many RAM should i expect to handle this kind of load?

    Is it better to have 1 zabbix server per dc + few minor proxies, or maybe one uber server?
    I have no need to distribute proxies accross multiple network zones.


    Thank you in advance!

  • cyber
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Dec 2006
    • 4806

    #2
    Definitely spread the load of polling to proxies... doing all that from one server is impossible.. Let proxies do polling and server do calculations
    Zabbix does not have such "umbrella" option right now, that you can have 2 separate isntances and view everythign from one "umbrella" instance.. Having one instance per DC will force you to look on 2 different screens etc.. If you do not have somekind of 3rd tool, where to forward everything...
    I would go with one instance and proxies in both DC-s. Unfortunately buil-in proxy HA does not work well with SNMP (no traps, for example). But if no trapping is required, you can think about it...
    You can stil build proxy clusters with pacemaker/corosync, so you will not lose much anything if some VM decides to give up a ghost... For my experience, startup of another instance is matter of seconds... For me this still looks better than buil-in HA...

    I dont know to what kind of NVPS this current 110k polls per minute from other tool translates... I don't think it is directly convertable by /60.. A proxy is good for 6-700 nvps.. sometimes more.. depending, how you build it, what DB you use etc.. But considering the amount of devices... Start with ... maybe 10-12 of them (5-6 proxies per DC)... In our case, 4cpu, 12G memory. It can run 2 proxies at the time, if half of cluster is dead...sqlite3 db on /dev/shm.. You may not need to run 2 per host, if you have some backup hosts in cluster.. Might get away with smaller hosts then...
    You can always add, if they get overloaded...

    Comment

    Working...