Hi
Currently I'm evaluating to install zabbix in our network. This will be a complete new installation, we currently have no monitoring wich is worth mentioning. As we are not moving from some other product, we don't need to care about any residues.
We have about 10 locations with several serveral servers (mostly windows), a bunch of switches (mostly hp), and between 80 and 150 wireless accesspoints. All of this is connected via vpn. The servers and the firewalls / vpn endpoints should get full monitoring (cpu, network, memory, diskspace etc.). For the switches / accesspoints we only need to know if they're connected to the network or not (ping).
Additionally we need to check for each location the availability of some specific servers wich are not under out control.
We're planning to set up a zabbix main server wich monitors only itself together with some other hardware/servers at a datacenter. Everything else should be done with proxys. Ideally we can put a preconfigured zabbix-proxy to each location so the guys over there just need to plug it in. As for now we are not sure if every location should get its own frontend, running at an on-site lamp-server or if they all should acces the frontend of the mainserver. The operating system for the mainserver will most likely be debian linux or FreeBSD with MySQL as database, the proxys will run on debian. Depending on the locationsize the proxys will use sqlite or mysql for their own database.
Unfortunatly as for now, I wasn't able to find much information about the hardware we need for the proxy and the bandwidth usage we can expect in our scenario.
Can anyone here give me some rough information about this or a hint where to find it? While the manual outlines the ressource usage of a mainserver, the data regarding proxys is quite sparse.
If more information is needed I'm happy to provide it.
with kind regards,
errorsmith
Currently I'm evaluating to install zabbix in our network. This will be a complete new installation, we currently have no monitoring wich is worth mentioning. As we are not moving from some other product, we don't need to care about any residues.
We have about 10 locations with several serveral servers (mostly windows), a bunch of switches (mostly hp), and between 80 and 150 wireless accesspoints. All of this is connected via vpn. The servers and the firewalls / vpn endpoints should get full monitoring (cpu, network, memory, diskspace etc.). For the switches / accesspoints we only need to know if they're connected to the network or not (ping).
Additionally we need to check for each location the availability of some specific servers wich are not under out control.
We're planning to set up a zabbix main server wich monitors only itself together with some other hardware/servers at a datacenter. Everything else should be done with proxys. Ideally we can put a preconfigured zabbix-proxy to each location so the guys over there just need to plug it in. As for now we are not sure if every location should get its own frontend, running at an on-site lamp-server or if they all should acces the frontend of the mainserver. The operating system for the mainserver will most likely be debian linux or FreeBSD with MySQL as database, the proxys will run on debian. Depending on the locationsize the proxys will use sqlite or mysql for their own database.
Unfortunatly as for now, I wasn't able to find much information about the hardware we need for the proxy and the bandwidth usage we can expect in our scenario.
Can anyone here give me some rough information about this or a hint where to find it? While the manual outlines the ressource usage of a mainserver, the data regarding proxys is quite sparse.
If more information is needed I'm happy to provide it.
with kind regards,
errorsmith
Comment