Guys
Been lurking around here for a while now and have a pretty good understanding of Zabbix and how she works. Needless to say, we have it deployed in our organisation.
It would be great if there was an agent that did not need the ports forwarded on the routers of remote sites for communication. This would be similar to what Kaseya do and a few others. I know a proxy is available, but they seem overkill when there are 4 pc's on a remote site and 200 remote sites!
Basically, the agent initiates a connection to the server every x seconds and requests its "config". If its changed, request the new config, otherwise the agent runs with its current config.
The agent will then pass the results of its tests/items back to the server as defined in the config. If the agent cannot communicate with the server for a specified interval, then the agent is presumed unavailable and is flagged up on Zabbix as such.
This allows all configuration for the agents to remain on the server and be requested as needed. The agents only need an address to "phone home". The agent makes the connection so no firewall modifications are required.
This could be achievable using something like XML over RPC. These are available on multiple platforms so could work with win,linux, mac etc
Thanks
Rick
Been lurking around here for a while now and have a pretty good understanding of Zabbix and how she works. Needless to say, we have it deployed in our organisation.
It would be great if there was an agent that did not need the ports forwarded on the routers of remote sites for communication. This would be similar to what Kaseya do and a few others. I know a proxy is available, but they seem overkill when there are 4 pc's on a remote site and 200 remote sites!
Basically, the agent initiates a connection to the server every x seconds and requests its "config". If its changed, request the new config, otherwise the agent runs with its current config.
The agent will then pass the results of its tests/items back to the server as defined in the config. If the agent cannot communicate with the server for a specified interval, then the agent is presumed unavailable and is flagged up on Zabbix as such.
This allows all configuration for the agents to remain on the server and be requested as needed. The agents only need an address to "phone home". The agent makes the connection so no firewall modifications are required.
This could be achievable using something like XML over RPC. These are available on multiple platforms so could work with win,linux, mac etc
Thanks
Rick
Comment