netbox-zabbix-sync: Add/delete host fails with proxy contexts added

We are testing the Netbox to Zabbix 7.0 integration and adding a host via the script using the standard snmpv2 that it defaults to works great. If I try to use a config context to assign an agent interface and/or set the host to be monitored via a proxy the script throws errors and exits.

Sometimes I get a log output but mostly I get netbox-zabbix-sync exited with code 0 with nothing else helpful.

Here’s the rendered context that is being apply by a tag:

{
    "zabbix": {
        "interface_port": 10500,
        "interface_type": 1
    }
}

Rendered config then using the proxy, redacted servername

{
    "zabbix": {
        "proxy": "servername"
    }
}

Template is being applied by a custom parameter and for now is set to ICMP Ping:

Zabbix template ICMP Ping

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 18 (18 by maintainers)

Commits related to this issue

Most upvoted comments

Seems that with tag filtering the Netbox API sets the operation to a logical AND instead of OR 😦 More information here: https://demo.netbox.dev/static/docs/rest-api/filtering/

For example with the following filter i only get devices which have both tags applied. `nb_device_filter = {“tag”: [“z1”, “z2”]

I’ll fall back to my original plan, I’ll have a single tag that the script will look for to add it to Zabbix then have another tag(s) to define proxy/agent types. A little messy, but still doable.

Here’s a Netbox thread confirming the same thing we are discussing here. If a logical “OR” is needed then it would need to be done client side. https://github.com/netbox-community/netbox/discussions/11703