You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow for some form of dynamic data allocation per Netbox device object. This could be useful for many instances.
One useful example would be mapping the primary cluster member name to a macro. After that Zabbix could trigger based on the current active cluster member name == macro (with data from Netbox.)
This step would shift the control plane for macro's one step further down into Netbox.
The text was updated successfully, but these errors were encountered:
I won't pick this up any time soon due to time constraints and the low priority. Should anyone be interested please make sure to vote on this issue since it helps me dedicate time to feature requests.
I Would like to start work on this. I'm thinking of something along the lines of the following:
Allowing for mapping NetBox fields to usermacros in the same way we can use the current inventory map, giving the possibility to use most NetBox static data in usermacros.
Allowing for mapping arbitrary config context keys to usermacros allowing for greater flexibility in usermacro overrides when needed.
Should be applicable to devices and vms, off course.
Allow for some form of dynamic data allocation per Netbox device object. This could be useful for many instances.
One useful example would be mapping the primary cluster member name to a macro. After that Zabbix could trigger based on the current active cluster member name == macro (with data from Netbox.)
This step would shift the control plane for macro's one step further down into Netbox.
The text was updated successfully, but these errors were encountered: