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

Allow filtering modules by device, location, tenant, or site #10619

New Issue
Closed
opened 2025-12-29 21:33:47 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:33:47 +01:00
Owner
Copy Link

Originally created by @forgottenroot on GitHub (Jan 7, 2025).

Originally assigned to: @arthanson on GitHub.

NetBox version

v4.2.0

Feature type

New functionality

Triage priority

I'm a NetBox Labs customer

Proposed functionality

In the modules view under filter you would be able to sort by devices, locations, sites, or tenants. There are currently only 5 fields to filter the table.
image

Use case

The current filtering on modules is very limited. This would allow you to see where modules are located/assigned to instead of having to use an external script. Expansion of https://github.com/netbox-community/netbox/issues/8810

Database changes

No response

External dependencies

No response

Originally created by @forgottenroot on GitHub (Jan 7, 2025). Originally assigned to: @arthanson on GitHub. ### NetBox version v4.2.0 ### Feature type New functionality ### Triage priority I'm a NetBox Labs customer ### Proposed functionality In the modules view under filter you would be able to sort by devices, locations, sites, or tenants. There are currently only 5 fields to filter the table. ![image](https://github.com/user-attachments/assets/856df1a7-9db9-420e-86c1-fa3a427db6ed) ### Use case The current filtering on modules is very limited. This would allow you to see where modules are located/assigned to instead of having to use an external script. Expansion of https://github.com/netbox-community/netbox/issues/8810 ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 21:33:47 +01:00
adam closed this issue 2025-12-29 21:33:47 +01:00
adam commented 2025-12-29 21:33:48 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 20, 2025):

FYI it is currently possible to filter modules by device_id. We should at least add that filter to the UI form. Filtering by device site/location makes sense IMO, however modules are not assigned to tenants (this is done via the parent device).

@jeremystretch commented on GitHub (Feb 20, 2025): FYI it is currently possible to filter modules by `device_id`. We should at least add that filter to the UI form. Filtering by device site/location makes sense IMO, however modules are not assigned to tenants (this is done via the parent device).
adam commented 2025-12-29 21:33:48 +01:00
Author
Owner
Copy Link

@the-seppel commented on GitHub (Mar 3, 2025):

@jeremystretch the filter of modules by location does make sense if you want to generate a list with all modules which belongs to a tenant / location.

@the-seppel commented on GitHub (Mar 3, 2025): @jeremystretch the filter of modules by location does make sense if you want to generate a list with all modules which belongs to a tenant / location.
adam commented 2025-12-29 21:33:48 +01:00
Author
Owner
Copy Link

@tgrusendorf commented on GitHub (Mar 14, 2025):

Adding some notes from a discussion with Mark Coleman today regarding the use case of NetBox as an asset inventory for Operational Technology (OT) / Industrial Control System (ICS) assets.

When we model OT assets in NetBox, we probably have an abnormally high usage of modules vs devices. Many of our assets are built with modules installed into passive chassis, not dissimilar to a chassis-based switch (example here). We've chosen to use module bays over device bays because the modules share a control plane.

Because we are very module-focused we often want to perform filters for a certain module type in a specific location or at a specific site. We also use Tenants to assign team responsibility and manage permissions for different assets.

All this is to say that this feature request would be very helpful to support our OT use cases.

While I understand that tenant is a device property, it would be helpful to be able to also filter modules by their parent device tenant. To me this is similar to the way that we allow the device view to be filtered by region.

@tgrusendorf commented on GitHub (Mar 14, 2025): Adding some notes from a discussion with Mark Coleman today regarding the use case of NetBox as an asset inventory for Operational Technology (OT) / Industrial Control System (ICS) assets. When we model OT assets in NetBox, we probably have an abnormally high usage of modules vs devices. Many of our assets are built with modules installed into passive chassis, not dissimilar to a chassis-based switch (example [here](https://instrumentationblog.com/plc-rack-and-plc-chassis/)). We've chosen to use module bays over device bays because the modules share a control plane. Because we are very module-focused we often want to perform filters for a certain module type in a specific location or at a specific site. We also use Tenants to assign team responsibility and manage permissions for different assets. All this is to say that this feature request would be very helpful to support our OT use cases. While I understand that tenant is a device property, it would be helpful to be able to also filter modules by their parent device tenant. To me this is similar to the way that we allow the device view to be filtered by region.
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 complexity: low 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#10619
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?