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

Searching by tag #1979

New Issue
Closed
opened 2025-12-29 17:21:05 +01:00 by adam · 6 comments
adam commented 2025-12-29 17:21:05 +01:00
Owner
Copy Link

Originally created by @rgrueebler on GitHub (Aug 30, 2018).

Hi everyone,

Environment

  • Python version: 2.7.5
  • NetBox version: 2.4.4

Proposed Functionality

It would be nice if I could search by tags.

Use Case

I add the same tag to different things like rack, device and ip address. Then I navigate to the rack and click on the tag. I expect NetBox to show the device and the ip address. With this feature it would be possible to group different things together. For example, I could group a customer to all the associated switch ports.
An alternative would be to add the "tenant" field to the interfaces. So it would be possible to associate a customer to the particular interfaces.

Database Changes

External Dependencies

Originally created by @rgrueebler on GitHub (Aug 30, 2018). <!-- NOTE: This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> Hi everyone, ### Environment * Python version: 2.7.5 * NetBox version: 2.4.4 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality It would be nice if I could search by tags. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case I add the same tag to different things like rack, device and ip address. Then I navigate to the rack and click on the tag. I expect NetBox to show the device and the ip address. With this feature it would be possible to group different things together. For example, I could group a customer to all the associated switch ports. An alternative would be to add the "tenant" field to the interfaces. So it would be possible to associate a customer to the particular interfaces. <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies
adam closed this issue 2025-12-29 17:21:06 +01:00
adam commented 2025-12-29 17:21:06 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 5, 2018):

It would be nice if I could search by tags.

Please elaborate on the specific functionality being proposed.

@jeremystretch commented on GitHub (Sep 5, 2018): > It would be nice if I could search by tags. Please elaborate on the specific functionality being proposed.
adam commented 2025-12-29 17:21:06 +01:00
Author
Owner
Copy Link

@rgrueebler commented on GitHub (Sep 10, 2018):

I'd like to know which customer is connected to which switch port. In our case this would be great, because we charge our customers the number of ports they use in our datacenter. So if I could click on the particular customer and see how many switch ports are associated to him, it would be much easier for us.
I think the easiest way to achieve this is if it is possible to add a "tenant" to an interface. Another solution would be if I can add a tag to a tenant and an interface. By clicking on the tag I would like to see the tenant and the corresponding interfaces. In my opinion this is the more flexible way.

Thank you
Remo

@rgrueebler commented on GitHub (Sep 10, 2018): I'd like to know which customer is connected to which switch port. In our case this would be great, because we charge our customers the number of ports they use in our datacenter. So if I could click on the particular customer and see how many switch ports are associated to him, it would be much easier for us. I think the easiest way to achieve this is if it is possible to add a "tenant" to an interface. Another solution would be if I can add a tag to a tenant and an interface. By clicking on the tag I would like to see the tenant and the corresponding interfaces. In my opinion this is the more flexible way. Thank you Remo
adam commented 2025-12-29 17:21:06 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 10, 2018):

Are you modeling the customer devices as well, or just "marking" each interface as being occupied by a particular customer?

@jeremystretch commented on GitHub (Sep 10, 2018): Are you modeling the customer devices as well, or just "marking" each interface as being occupied by a particular customer?
adam commented 2025-12-29 17:21:06 +01:00
Author
Owner
Copy Link

@rgrueebler commented on GitHub (Sep 10, 2018):

We don't document the customer devices. This would be too much work. We only would like to mark the interface as being occupied by a customer.

Thank you
Remo

@rgrueebler commented on GitHub (Sep 10, 2018): We don't document the customer devices. This would be too much work. We only would like to mark the interface as being occupied by a customer. Thank you Remo
adam commented 2025-12-29 17:21:06 +01:00
Author
Owner
Copy Link

@vsvetlov commented on GitHub (Sep 26, 2018):

I have some thoughts about that.
Currently, the only way to find a prefix or IP address is using prefix or IP address as the value for search. But there is a use case when you want to find all the prefixes/address for example associated with mail-servers using tags or custom fields feature. For that you should use filtering feature by clicking on the specific tag or choosing custom field's value in a list. When you have a lot of tags it is not the best way to search and implementing a search feature for tags looks reasonable in that case.

@vsvetlov commented on GitHub (Sep 26, 2018): I have some thoughts about that. Currently, the only way to find a prefix or IP address is using prefix or IP address as the value for search. But there is a use case when you want to find all the prefixes/address for example associated with mail-servers using tags or custom fields feature. For that you should use filtering feature by clicking on the specific tag or choosing custom field's value in a list. When you have a lot of tags it is not the best way to search and implementing a search feature for tags looks reasonable in that case.
adam commented 2025-12-29 17:21:07 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 1, 2018):

Closing this out as it is not sufficiently detailed.

@jeremystretch commented on GitHub (Nov 1, 2018): Closing this out as it is not sufficiently detailed.
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
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#1979
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?