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

Status indicators in rack view #1648

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

Originally created by @WardsParadox on GitHub (Mar 28, 2018).

Issue type

[X] Feature request
[ ] Bug report
[ ] Documentation

Environment

  • Python version: 2.7.12
  • NetBox version: v2.3.1)

Description

Currently, when looking at a rack view, you can see different types of devices. This is great. What you can't see at a quick glance is their status. You have to click on the unit and view the status. If one could see the status from either hovering on top of the item in the rack OR via a set of patterns in the coloring, such as a striped pattern in red for failed with the base color of the device role.
Gray could be offline, red for failed, planned could be blue, stagged could be green, active would just be the base color, etc.

Originally created by @WardsParadox on GitHub (Mar 28, 2018). <!-- Before opening a new issue, please search through the existing issues to see if your topic has already been addressed. Note that you may need to remove the "is:open" filter from the search bar to include closed issues. Check the appropriate type for your issue below by placing an x between the brackets. For assistance with installation issues, or for any other issues other than those listed below, please raise your topic for discussion on our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please note that issues which do not fall under any of the below categories will be closed. Due to an excessive backlog of feature requests, we are not currently accepting any proposals which extend NetBox's feature scope. Do not prepend any sort of tag to your issue's title. An administrator will review your issue and assign labels as appropriate. ---> ### Issue type [X] Feature request <!-- An enhancement of existing functionality --> [ ] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> <!-- Please describe the environment in which you are running NetBox. (Be sure to verify that you are running the latest stable release of NetBox before submitting a bug report.) If you are submitting a bug report and have made any changes to the code base, please first validate that your bug can be recreated while running an official release. --> ### Environment * Python version: 2.7.12 <!-- Example: 3.5.4 --> * NetBox version: v2.3.1) <!-- Example: 2.1.3 --> <!-- BUG REPORTS must include: * A list of the steps needed for someone else to reproduce the bug * A description of the expected and observed behavior * Any relevant error messages (screenshots may also help) FEATURE REQUESTS must include: * A detailed description of the proposed functionality * A use case for the new feature * A rough description of any necessary changes to the database schema * Any relevant third-party libraries which would be needed --> ### Description Currently, when looking at a rack view, you can see different types of devices. This is great. What you can't see at a quick glance is their status. You have to click on the unit and view the status. If one could see the status from either hovering on top of the item in the rack OR via a set of patterns in the coloring, such as a striped pattern in red for failed with the base color of the device role. Gray could be offline, red for failed, planned could be blue, stagged could be green, active would just be the base color, etc.
adam closed this issue 2025-12-29 16:33:48 +01:00
adam commented 2025-12-29 16:33:48 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 29, 2018):

I like it, but we need to decide how best to display status. I don't really like the hover option; it would be more useful to see the status of every device at a glance. I also want to keep the current coloring of devices by role. Maybe a toggle button at the top to show/hide a 'status' overlay?

@jeremystretch commented on GitHub (Mar 29, 2018): I like it, but we need to decide how best to display status. I don't really like the hover option; it would be more useful to see the status of every device at a glance. I also want to keep the current coloring of devices by role. Maybe a toggle button at the top to show/hide a 'status' overlay?
adam commented 2025-12-29 16:33:48 +01:00
Author
Owner
Copy Link

@Yakelixir commented on GitHub (Mar 29, 2018):

Yeah in respect to signal to noise a toogle for this would work in regards to display.

Thoughts on display via toggle...

  • box on the side of the device that overlays a color/string/etc (might be cool to be customizable)
  • string with color
  • symbol w/wo color
  • etc

Might work. #designchoices

@Yakelixir commented on GitHub (Mar 29, 2018): Yeah in respect to signal to noise a toogle for this would work in regards to display. Thoughts on display via toggle... - box on the side of the device that overlays a color/string/etc (might be cool to be customizable) - string with color - symbol w/wo color - etc Might work. #designchoices
adam commented 2025-12-29 16:33:49 +01:00
Author
Owner
Copy Link

@igorrev commented on GitHub (Apr 5, 2018):

Yes, it's really necessary feature. We are planning relocation of equipment and need to mark units in rack as reserved for particular devices.

I think, no color. Color is already used for device type and it's good. And no hover, of course. Status information must be visible without user interaction and in print view too.
Symbol is good idea. May be inside device bar in rack or outside device bar on the right of the rack, similar to unit numbers.

@igorrev commented on GitHub (Apr 5, 2018): Yes, it's really necessary feature. We are planning relocation of equipment and need to mark units in rack as reserved for particular devices. I think, no color. Color is already used for device type and it's good. And no hover, of course. Status information must be visible without user interaction and in print view too. Symbol is good idea. May be inside device bar in rack or outside device bar on the right of the rack, similar to unit numbers.
adam commented 2025-12-29 16:33:49 +01:00
Author
Owner
Copy Link

@Yakelixir commented on GitHub (Apr 10, 2018):

Until this is implemented I would use one of the following methods for marking devices as in transit.

  • Updates to the hostname name to reflect [string changes] new rsvd etc status
  • Change devices status to offline (your choice here on status however since its all subjective). Devices are usually online so this applies to dead/repair/planned hosts. Change back when events/issues are cleared

I would recommend patch requests for this unless it is a small enough amount of devices to manually change values. So of my comments below come with the assuming that a tertiary relational DB exists and that you will be updating some of your values via some scripting.

@Yakelixir commented on GitHub (Apr 10, 2018): Until this is implemented I would use one of the following methods for marking devices as `in transit`. - Updates to the hostname name to reflect [string changes] `new` `rsvd` `etc` status - Change devices status to offline (your choice here on status however since its all subjective). _Devices are usually online so this applies to dead/repair/planned hosts. Change back when events/issues are cleared_ I would recommend patch requests for this unless it is a small enough amount of devices to manually change values. So of my comments below come with the assuming that a tertiary relational DB exists and that you will be updating some of your values via some scripting.
adam commented 2025-12-29 16:33:50 +01:00
Author
Owner
Copy Link

@pm17788 commented on GitHub (May 7, 2018):

Since there is MarkDown support already in the code, perhaps prefix (or suffix) the name of the device in the rack with one of the:

Status Options
Failed ❗ or 🆘
Offline 💤 or ⚪ or 🔳
Planned ❔
Staged ✅
Active ✔️

Regardless of what is chosen, please let's add a legend visible somewhere on the page?

@pm17788 commented on GitHub (May 7, 2018): Since there is MarkDown support already in the code, perhaps prefix (or suffix) the name of the device in the rack with one of the: | Status | Options | | ------------- |:-------------:| | Failed | :exclamation: or :sos: | | Offline | :zzz: or :white_circle: or :white_square_button: | | Planned | :grey_question: | | Staged | :white_check_mark: | | Active | :heavy_check_mark: | Regardless of what is chosen, please let's add a legend visible somewhere on the page?
adam commented 2025-12-29 16:33:52 +01:00
Author
Owner
Copy Link

@ankerstal commented on GitHub (May 7, 2018):

I really need this as well. My suggestion is some sort of "pattern" since color is already used for type.

@ankerstal commented on GitHub (May 7, 2018): I really need this as well. My suggestion is some sort of "pattern" since color is already used for type.
adam commented 2025-12-29 16:33:59 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 18, 2018):

We might want to shelve this idea and see if #2248 (HTML5 canvas-based rendering) gains traction.

@jeremystretch commented on GitHub (Jul 18, 2018): We might want to shelve this idea and see if #2248 (HTML5 canvas-based rendering) gains traction.
adam commented 2025-12-29 16:33:59 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 31, 2018):

After experimenting with SVG-based rendering (#2248), it seems like a much more preferable approach than how we currently render racks. It'll take a bit of work but I hope to fold it into the 2.4 train at some point in the near future. I'm going to close this out since I'm sure whatever we come with will incorporate status illustration in some manner. SVG opens up a lot of possibilities.

@jeremystretch commented on GitHub (Jul 31, 2018): After experimenting with SVG-based rendering (#2248), it seems like a _much_ more preferable approach than how we currently render racks. It'll take a bit of work but I hope to fold it into the 2.4 train at some point in the near future. I'm going to close this out since I'm sure whatever we come with will incorporate status illustration in some manner. SVG opens up a lot of possibilities.
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#1648
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?