NeoAnd/netbox-zabbix-sync
1
0
Fork 0
mirror of https://github.com/TheNetworkGuy/netbox-zabbix-sync.git synced 2025-07-14 09:51:26 -06:00
Code Issues Actions Packages Projects Releases Wiki Activity

Updated README with Proxy details and -p flag

Browse Source
This commit is contained in:
Twan Kamans 2021-07-16 20:02:08 +02:00
parent 135c04af98
commit 92e9a1149c
1 changed files with 12 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
README.md
View File

@ -22,7 +22,7 @@ Optional:
| -t | tenant | Add the tenant name to the hostgroup format (Tenant/Site/Manufacturer/Role) |
| -s | secret | Use Netbox secrets if present on device for SNMP parameters
| -v | verbose | Log with debugging on. |
| -p | proxy-power | Force a full proxy sync. USE WITH CAUTION, see "Set proxy within Netbox" for more information |
#### Logging
Logs are generated under sync.log, use -v for debugging.
@ -56,6 +56,17 @@ And this field for the Zabbix template
* Default: null
* Object: dcim > device_type
#### Set proxy within Netbox
You can set the proxy for a device using the 'proxy' key in config context.
```json
{
"zabbix": {
"proxy": "yourawesomeproxy.local"
}
}
```
Because of the posible amount of destruction when setting up Netbox but forgetting the proxy command, the sync works a bit different. By default everything is synced except in a situation where the Zabbix host has a proxy configured but nothing is configured in Netbox. To force deletion and a full sync, use the -p flag.
#### Set interface parameters within Netbox
When adding a new device, you can set the interface type with custom context.
Due to Zabbix limitations of changing interface type with a linked template, changing the interface type from within Netbox is not supported and the script will generate an error.