Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
forgottenroot opened this issue Jan 7, 2025 · 3 comments · Fixed by #19312
Closed

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

forgottenroot opened this issue Jan 7, 2025 · 3 comments · Fixed by #19312
Assignees
Labels
complexity: low Requires minimal effort to implement status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Milestone

Comments

@forgottenroot
Copy link

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 #8810

Database changes

No response

External dependencies

No response

@forgottenroot forgottenroot added status: needs triage This issue is awaiting triage by a maintainer type: feature Introduction of new functionality to the application labels Jan 7, 2025
@jeremystretch jeremystretch added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation complexity: low Requires minimal effort to implement and removed status: needs triage This issue is awaiting triage by a maintainer labels Feb 20, 2025
@jeremystretch
Copy link
Member

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).

@the-seppel
Copy link

@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.

@tgrusendorf
Copy link

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.

@arthanson arthanson self-assigned this Apr 24, 2025
@arthanson arthanson added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Apr 24, 2025
@jeremystretch jeremystretch added this to the v4.2.9 milestone Apr 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity: low Requires minimal effort to implement status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants