Jinja2 Variable Support for Zabbix Inventory Fields

[taofineberg]

Is it possible to use Jinja2 variables in the Inventory configuration?

Use Case
It would be extremely useful to sync inventory data (e.g., Latitude/Longitude, address, location details, etc.) from NetBox to Zabbix automatically, rather than manually populating each field with data that already exists in NetBox.

Proposed Solution
Ideally, this functionality could be added to the new Configuration Group feature—which is a great addition, by the way!

Related Work / Findings
I was able to get Jinja2 variables working for Tags and Host Groups by modifying the following files to extend the context:

zabbixtagassignment.py - Adds site, tenant, role, device_type, manufacturer to ZabbixTagAssignment.get_context()
zabbixhostgroupassignment.py - Adds site, tenant, role, device_type, manufacturer to ZabbixHostgroupAssignment.get_context()

Then use
{{ manufacturer.name }}
{{ site.name }}
{{ device_type.model }}

[adparis99]

I also think this would be a great feature to add!

[bvbaekel]

Hi!

This is absolutely possible, as least at Host Inventory level.

results in

object refers to the NetBox Object (device, vdc, vm) this inventory is created for, and then you can refer to the related objects, for example site, device_type, et cetera.

It should be possible to add this to Configuration Groups as well; as it just 'copy and pastes' the configuration/templated item. I'll dig into this when I have time!

[taofineberg]

Thanks that would be great.
There seems to be some validation issue also for the lat/long when trying yo use jinja2

[bvbaekel]

Thanks, the fix for lat/long will be included in the next release, :)

Please note the correct syntax would be {{ object.site.latitude }}
'object' refers to the device/vm/vdc in this case; site refers to the assigned site and latitude selected the 'latitude' field on the Site object.

As mentioned, when I have time - I'll see if I can get this working with configuration groups.

[bvbaekel]

Lat/Long fix is included in v1.0.2 - which has been released.