[ZBXNEXT-7073] Ability to send the configuration to a Pasive Proxy Created: 2021 Nov 25 Updated: 2022 Sep 20 Resolved: 2022 Sep 20 |
|
| Status: | Closed |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Proxy (P) |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature Request | Priority: | Medium |
| Reporter: | Gustavo Guido | Assignee: | Andris Zeila |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
a comand like
zabbix_server -R config_cache:_reload=proxyName
in order to push the configuration to a pasive proxy |
| Comments |
| Comment by Gustavo Guido [ 2021 Nov 26 ] |
|
Thinking a bit more on this, may be is a good idea to even update the active proxys from the frontend or server. If we claim that the configuration is centralized, and the proxy could be behind a firewall that does not aloud a ssh connection, it will be necessary to wait for a hour for the change in configuration to take effect. Creating a task for the active proxy to reload the configuration will short this time and all all be centralized |
| Comment by Gustavo Guido [ 2022 Sep 07 ] |
|
I think this can be close, since it is already developed |