Announcement

Collapse
No announcement yet.

discovery action to assign a host to a proxy

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

    discovery action to assign a host to a proxy

    I would like to configure a zabbix proxy per /24 network.

    I'll have each host check for the existence of a machine named zabbix-<my 3rd octet>, and if it is found, modify the zabbix_agentd.conf and insert that hostname in front of the default server.

    For example a host with IP 10.10.183.1 gets:
    Code:
    Server=zabbix-183.domain.com,zabbix.domain.com
    However, there doesn't seem to be a Discovery Action Operation available to assign a host to a proxy.

    Is there some way to assign a host to a proxy using discovery?

    #2
    alternate solution

    I found out the hard way, that if you assign an auto-discovery rule to a proxy then the hosts are assigned to that proxy automatically. That's handy if your hosts know about the proxy.

    However, if all those hosts are already known, and the proxy is not listed as the Server in the zabbix_agentd.conf, then once those hosts are rediscovered the agents will go 'unreachable' and your pager will explode.

    So, if you use autodiscovery, disable the zabbix {Template_Linux:status.last(0)}=2 trigger during a migration to a new proxy and do it in a timely fashion.

    Comment

    Working...
    X