Requirements for a setup with proxies

[spidernik84]

Hi all,

we're currently running five different zabbix servers placed in different sites and we're considering to change our architecture to a single master - multiple proxies setup.
I have a few questions:

1. is there any requirements document that shows how much bandwidth the proxy is going to consume per amount of nvps?
2. what are the suggested hardware/database specifications for the proxies? I need in particular to evaluate wheter to use postgres or sqllite as a database depending on the number of items/hosts
3. talking about documents: any suggested procedure to do the migration? I was thinking of just setting up the proxies and rename them to "take over" the secondary masters, so the agents are unaware of starting to be monitored by the proxies
4. I'd also suggest to make a survey amongst your customer to know the hardware configurations they use on their servers, their nvps and the monitored hosts, and to place the statistics in the documentation. This way one can plan ahead the resources needed depending on the setup.

[spidernik84]

Anyone with the same requirements?

[mushero]

Some thoughts:

1) Bandwidth very small from our experience and usually sent in blocks when busy so very fast and maybe 100kbps for 100 servers, at 100nvps, not sure.

2) Our proxies are small, maybe 2-4GB RAM 2-4 CPUs VMs. Not much load, though some I/O.
3) Migration for what ? We setup proxy, open host firewall/config / IP and then just move hosts over in main server (we are 100% passive agents).
4) We are 500Nvps on thousands of hosts, 250K items, 100K triggers, etc. on 8 core 64-96GB RAM, very fast disks. Proxies are up to 100 Nvps.

Hi all,

we're currently running five different zabbix servers placed in different sites and we're considering to change our architecture to a single master - multiple proxies setup.
I have a few questions:

1. is there any requirements document that shows how much bandwidth the proxy is going to consume per amount of nvps?
2. what are the suggested hardware/database specifications for the proxies? I need in particular to evaluate wheter to use postgres or sqllite as a database depending on the number of items/hosts
3. talking about documents: any suggested procedure to do the migration? I was thinking of just setting up the proxies and rename them to "take over" the secondary masters, so the agents are unaware of starting to be monitored by the proxies
4. I'd also suggest to make a survey amongst your customer to know the hardware configurations they use on their servers, their nvps and the monitored hosts, and to place the statistics in the documentation. This way one can plan ahead the resources needed depending on the setup.

[spidernik84]

Some thoughts:

3) Migration for what ? We setup proxy, open host firewall/config / IP and then just move hosts over in main server (we are 100% passive agents).

Hi,

migration of the hosts from the dedicated autonomous servers to the proxies.
The initial plan was to keep the same hostname of the servers to avoid changing the server and serveractive parameters in the agents' configurations. We're going to use a different hostname for the proxies and modify the agents configurations, I suppose.

4) We are 500Nvps on thousands of hosts, 250K items, 100K triggers, etc. on 8 core 64-96GB RAM, very fast disks. Proxies are up to 100 Nvps.

Thanks for your report.
We're going for sqllite on the proxies I think. It should be good for a while.