How to separate auto registration between two proxies in the same network

[kaloyan.s]

Hello,

We have faced an issue with one of our proxies - stopped sending/collecting data to the master, which is 200 ms away from the zabbix master. I have installed second proxy and balanced the hosts manually.
However when i create a separate auto registration rule for each proxy and enable them, the hosts are constantly auto-registered from one proxy to the other, therefore not able to be monitored properly.

Has anyone faced such issue before ?
Does anyone have an idea how to use two proxies with auto-registration in the same network ?

Regards,
Kaloyan

[kloczek]

Hello,

We have faced an issue with one of our proxies - stopped sending/collecting data to the master, which is 200 ms away from the zabbix master. I have installed second proxy and balanced the hosts manually.
However when i create a separate auto registration rule for each proxy and enable them, the hosts are constantly auto-registered from one proxy to the other, therefore not able to be monitored properly.

What you mean "I have installed second proxy"?
Did you start second proxy and it is visible to the monitored hosts under the same IP which is now service VIP?
It is not possible to use zabbix proxy that way.

PS. Your post should not be posted on "Zabbix for Large Environments" forum.

[kaloyan.s]

Hello,

I have installed second proxy and added its IP to all the hosts, which are already monitored. I want to separate the load on the proxies between two of them, but it seems with auto-registration the things will not work like that.
I am thinking of separating the monitored hosts between the two proxies with leaving only one of the IPs of the first proxy in the config for the half of the hosts and the other half with the IP of the second proxy.

Regards,

I moved the topic to Zabbix Troubleshooting and Problems, sorry for this.

[dimir]

You can list both proxies in agent config file e. g.

Server=1.1.1.1,2.2.2.2

it will just tell the agent to allow connections from those for passive checks. But you need to set only one of them for auto-registration.

Agent1 (registers to proxy 1.1.1.1):

Server=1.1.1.1,2.2.2.2
ServerActive=1.1.1.1

Agent2 (registers to proxy 2.2.2.2)

Server=1.1.1.1,2.2.2.2
ServerActive=2.2.2.2

[kloczek]

You can list both proxies in agent config file e. g.



it will just tell the agent to allow connections from those for passive checks. But you need to set only one of them for auto-registration.

Agent1 (registers to proxy 1.1.1.1):


Agent2 (registers to proxy 2.2.2.2)

Registering agent with more than one Server/ServerActive entries means that this single agent interact with two different zabbix monitoring stacks -> data sent to more than one ServerActive or sampled by more than one Server will land finally in two independent central zabbix databases.
In other words it will be not working with addresses of two proxies talking to one server.
Each zabbix agent in zabbix hosts table database is identified by single physical path server[<->proxy]<->agent.

[dimir]

I specifically noted that it should register with only one proxy. The Server= can have many, it will not do any harm because it's only there for passive checks.

[kloczek]

I specifically noted that it should register with only one proxy. The Server= can have many, it will not do any harm because it's only there for passive checks.

And in such case everything depends on type of the proxies.
If such proxies are active they will be querying about monitoring cfg data for the same proxy and if both proxies will be pooling for passive items it will instantly cause delivery duplicated data to the server.
If we are talking about two passive proxies server will be connecting to only one proxy and if over passive proxies active agent will be hitting time top time this proxy which doesn't know anything about exact agent monitoring cfg informing it that nothing needs to be monitored over such agent.

As I wrote: generally such duplication of the proxies does not make any sense.

[kaloyan.s]

Thanks @kloczek

In the end i just modified the zabbix agent config on the first batch of servers to use the first proxy and the second batch to use the second proxy.
All new machines (auto registration) will be done by second proxy as well until it gets overloaded, then will add third and so on.

Regards,
Kaloyan

[dimir]

And in such case everything depends on type of the proxies.
If such proxies are active they will be querying about monitoring cfg data for the same proxy and if both proxies will be pooling for passive items it will instantly cause delivery duplicated data to the server.
If we are talking about two passive proxies server will be connecting to only one proxy and if over passive proxies active agent will be hitting time top time this proxy which doesn't know anything about exact agent monitoring cfg informing it that nothing needs to be monitored over such agent.

As I wrote: generally such duplication of the proxies does not make any sense.

It looks like there is some misunderstanding here. There are millions of ways to set up Zabbix. I hope we are not discussing them here. For this particular case, as I understood, the agent should list one proxy for active checks and if there is any need to allow passive requests to the agent, he can list source hosts in Server= . I see nothing wrong in this configuration. For example, I usually list safe hosts in agents Server= to allow testing metrics using zabbix_get.