CentOS 6.4

In a large environment with many different hosts that needs to be checked for many different stuff this feature would be very nice to have.
ex. When you have actions basted on HotMetadata that you want to add a host to a group or template basted on what is in HostMetadata.
There is no way automatically added a host that is already in zabbix to a new template/group basted on a new item in HotMetadata
Lets say that you want to add all hosts that has a HP raid card to a HP-RAID-CARD template. If you specify a HP-RAID-CARD item in HostMetadata, you can have a action to add it to a template. This is not a problem for new hosts that are added with agent auto registration, but for hosts that already are added to zabbix you can not get it to automatically add the host to a new template.

Hello @alexei,

First thank you and all the community for the best monitoring software ever.

One question: there is any plan to implement this feature in the future, its in any future version road map?

I'm asking because if there is no plan then hostmetadata it's no fit for a full automated zabbix setup that is able to keep up to date.

Best regards from Montevideo,

Guzmán

HI @alexei,

That would be a real good option to be able to manage the host definition from the HostMetadata on a large scale setup.

I'm a Zabbix User since zabbix 1.4 and I'm really waiting for this feature.

The test case in my company is quite simple, thousand of servers (mostly unknowns by the current admins) and having zabbix_agent deployed through ansible and hostmetadata populated when adding new softwares.

Having to delete the host in zabbix is not a good option, we loose all the historical data.

Using the API is in my opinion overkill for that

keywords to ease searching : update existing repeated

Here's a useful semantic:

• Add "HostMetadata has changed since condition last evaluated" condition that can be used as an Action condition
• Add a (default on for new Actions) flag: Re-evaluate on ever Active contact.

This maintains semantic compatibility with existing environments while supporting the useful feature. It also permits multiple actions to apply to a newly-registered host.

My own use case for this: I want to compose HostMetadata in my Agent configuration from multiple Saltstack pillars, and as a node's role changes or expands, I want additional monitoring applied.

I could conceivably do it with the Zabbix API, but then I need to provide network access to the Zabbix front-end from nodes that wouldn't necessarily even have a network path to reach it in the first place. (Especially notable if passing through Zabbix proxies on the way.)

@mikemol we have a similar need, but satisfy it by raising a salt event and having a reactor run an orchestrate job on the zabbix server which ensures the modified host is in zabbix with all appropriate configurations.

create_host_group:
  zabbix_hostgroup.present:
    - name: {{ zab_hostgroup }}

create_host_{{ zab_host }}:
  zabbix_host.present:
    - host: {{ zab_host }}
    {% if zab_proxy -%}
    - proxy_host: {{ zab_proxy }}
    {% endif -%}
    - groups:
      - {{ zab_hostgroup }}
    - interfaces:
      - {{ zab_host }}:
        - ip: {{ zab_ip }}
        - type: 'Agent'
        - port: 10050

add_zabbix_templates_to_host:
  zabbix_host.assign_templates:
    - host: {{ zab_host }}
    - templates: {{ zab_templates }}

Available in:

• 4.0.0alpha8 (trunk) r81506