starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Config context by tags #2993

New Issue
Closed
opened 2025-12-29 18:24:29 +01:00 by adam · 4 comments
adam commented 2025-12-29 18:24:29 +01:00
Owner
Copy Link

Originally created by @itmicus on GitHub (Nov 3, 2019).

Originally assigned to: @kobayashi on GitHub.

Environment

  • Python version: 3.7.3
  • NetBox version: 2.6.6

Proposed Functionality

Add to the config context assignment field with tags

Use Case

I use the tag "monitored_by_zabbix" for devices and VMs wich will be monitoring in our Zabbix system.
I want to create config contex with config for Zabbix for this devices/vms

Database Changes

Yes

External Dependencies

None

Originally created by @itmicus on GitHub (Nov 3, 2019). Originally assigned to: @kobayashi on GitHub. ### Environment * Python version: 3.7.3 * NetBox version: 2.6.6 ### Proposed Functionality Add to the config context assignment field with tags ### Use Case I use the tag "monitored_by_zabbix" for devices and VMs wich will be monitoring in our Zabbix system. I want to create config contex with config for Zabbix for this devices/vms ### Database Changes Yes ### External Dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 18:24:29 +01:00
adam closed this issue 2025-12-29 18:24:29 +01:00
adam commented 2025-12-29 18:24:30 +01:00
Author
Owner
Copy Link

@kobayashi commented on GitHub (Nov 8, 2019):

Could you give us more detail of your usecase step-by-step?

@kobayashi commented on GitHub (Nov 8, 2019): Could you give us more detail of your usecase step-by-step?
adam commented 2025-12-29 18:24:30 +01:00
Author
Owner
Copy Link

@wfrced commented on GitHub (Nov 15, 2019):

I believe I have a somewhat similar usecase, so will chime in.
With these changes I'd be able to:

  1. Get a list of hosts using Netbox plugin for Ansible;
  2. Create Ansible groups using tag names and add my hosts to these groups;
  3. Add tag's Config Context to group variables;
  4. Create/Update hosts in Zabbix using Zabbix plugin for Ansible.

Basically, it would allow me to use tags as Ansible groups, and Config Contexts as group_vars.
Or I could simply store a more general Zabbix config for, say, a Tenant or a Site, and use tag's CC to store a boolean - whether to enable monitoring for this host.

@wfrced commented on GitHub (Nov 15, 2019): I believe I have a somewhat similar usecase, so will chime in. With these changes I'd be able to: 1. Get a list of hosts using Netbox plugin for Ansible; 2. Create Ansible groups using tag names and add my hosts to these groups; 3. Add tag's Config Context to group variables; 2. Create/Update hosts in Zabbix using Zabbix plugin for Ansible. Basically, it would allow me to use tags as Ansible groups, and Config Contexts as `group_vars`. Or I could simply store a more general Zabbix config for, say, a Tenant or a Site, and use tag's CC to store a boolean - whether to enable monitoring for this host.
adam commented 2025-12-29 18:24:30 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Dec 6, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@stale[bot] commented on GitHub (Dec 6, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 18:24:30 +01:00
Author
Owner
Copy Link

@kobayashi commented on GitHub (Dec 6, 2019):

I am taking this

@kobayashi commented on GitHub (Dec 6, 2019): I am taking this
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#2993
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?