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

Filter or highlight devices in rack elevation based on device attributes #3528

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

Originally created by @ryanmerolle on GitHub (Apr 1, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 2.6.9
  • NetBox version: 2.7.11

Proposed Functionality

Allow a device filter or highlight (ie fade devices not matching criteria) option in rack elevations based on device attributes like tag, platform, device type, manufacturer.

Use Case

This would be useful to view your racks and provide easier visibility of where devices of a similar attribute are physically racked.

Database Changes

N/A more of a front end tweak.

External Dependencies

N/A

Originally created by @ryanmerolle on GitHub (Apr 1, 2020). Originally assigned to: @jeremystretch on GitHub. ### Environment * Python version: 2.6.9 * NetBox version: 2.7.11 ### Proposed Functionality Allow a device filter or highlight (ie fade devices not matching criteria) option in rack elevations based on device attributes like tag, platform, device type, manufacturer. ### Use Case This would be useful to view your racks and provide easier visibility of where devices of a similar attribute are physically racked. ### Database Changes N/A more of a front end tweak. ### External Dependencies N/A
adam added the status: acceptedtype: feature labels 2025-12-29 18:29:39 +01:00
adam closed this issue 2025-12-29 18:29:40 +01:00
adam commented 2025-12-29 18:29:40 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Apr 1, 2020):

Not a major request, and I understand if you think its not worth the effort. I just had a user who wanted to see where exactly all devices of a particular tag were racked. Currently, there is no easy way to view this all in the rack elevations view.

@ryanmerolle commented on GitHub (Apr 1, 2020): Not a major request, and I understand if you think its not worth the effort. I just had a user who wanted to see where exactly all devices of a particular tag were racked. Currently, there is no easy way to view this all in the rack elevations view.
adam commented 2025-12-29 18:29:40 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 1, 2020):

I don't think we'd be able to use the filtersets for this, so it would need some new mechanism for indicating which devices to highlight. It's probably too much to ask for in the API natively at this point, and better suited to implementation directly within the UI. (For example, to highlight all device elements with foo in their data-tags property.)

I could see a partial implementation where we pass device IDs in the form ?render=svg&highlight=123&highlight=456. This could be useful for providing a "view in rack" link for individual devices (or in the case of virtual chassis, multiple devices).

@jeremystretch commented on GitHub (Apr 1, 2020): I don't think we'd be able to use the filtersets for this, so it would need some new mechanism for indicating which devices to highlight. It's probably too much to ask for in the API natively at this point, and better suited to implementation directly within the UI. (For example, to highlight all device elements with `foo` in their `data-tags` property.) I could see a partial implementation where we pass device IDs in the form `?render=svg&highlight=123&highlight=456`. This could be useful for providing a "view in rack" link for individual devices (or in the case of virtual chassis, multiple devices).
adam commented 2025-12-29 18:29:40 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Apr 1, 2020):

That does not sound like a bad approach at all.

@ryanmerolle commented on GitHub (Apr 1, 2020): That does not sound like a bad approach at all.
adam commented 2025-12-29 18:29:40 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Sep 7, 2020):

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 (Sep 7, 2020): 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:29:40 +01:00
Author
Owner
Copy Link

@dpotter-intoto commented on GitHub (Nov 4, 2021):

Please consider including device status when implementing this feature... how great would it be to generate a rack elevation that highlights all devices with the planned status or the decommissioning status?

@dpotter-intoto commented on GitHub (Nov 4, 2021): Please consider including **device status** when implementing this feature... how great would it be to generate a rack elevation that highlights all devices with the `planned` status or the `decommissioning` status?
adam commented 2025-12-29 18:29:40 +01:00
Author
Owner
Copy Link

@ekrichbaum commented on GitHub (Mar 8, 2022):

To avoid messing with the display of the rack elements themselves, set the color of the RU number background. I was originally thinking based on the role color and then having a role for deprecated, but assigning colors to the states of the device would work as well.

image

@ekrichbaum commented on GitHub (Mar 8, 2022): To avoid messing with the display of the rack elements themselves, set the color of the RU number background. I was originally thinking based on the role color and then having a role for deprecated, but assigning colors to the states of the device would work as well. ![image](https://user-images.githubusercontent.com/11653069/157252531-5f9fc6a6-3034-4ff0-9d1d-e26096893d8e.png)
adam commented 2025-12-29 18:29:41 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 7, 2022):

Per #9035 we should also support highlighting rack reservations.

@jeremystretch commented on GitHub (Apr 7, 2022): Per #9035 we should also support highlighting rack reservations.
adam commented 2025-12-29 18:29:41 +01:00
Author
Owner
Copy Link

@ITJamie commented on GitHub (May 26, 2022):

I don't think we'd be able to use the filtersets for this, so it would need some new mechanism for indicating which devices to highlight. It's probably too much to ask for in the API natively at this point, and better suited to implementation directly within the UI. (For example, to highlight all device elements with foo in their data-tags property.)

I could see a partial implementation where we pass device IDs in the form ?render=svg&highlight=123&highlight=456. This could be useful for providing a "view in rack" link for individual devices (or in the case of virtual chassis, multiple devices).

It would be nice if you navigate to the rack page from a device page via the U position link for it to automatically highlight the device on the rack view.

@ITJamie commented on GitHub (May 26, 2022): > I don't think we'd be able to use the filtersets for this, so it would need some new mechanism for indicating which devices to highlight. It's probably too much to ask for in the API natively at this point, and better suited to implementation directly within the UI. (For example, to highlight all device elements with `foo` in their `data-tags` property.) > > I could see a partial implementation where we pass device IDs in the form `?render=svg&highlight=123&highlight=456`. This could be useful for providing a "view in rack" link for individual devices (or in the case of virtual chassis, multiple devices). It would be nice if you navigate to the rack page from a device page via the U position link for it to automatically highlight the device on the rack view.
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#3528
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?