starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Show full 100% utilization bar in a different color from 99.9% #5878

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

Originally created by @bluikko on GitHub (Jan 5, 2022).

NetBox version

v3.1.4

Feature type

Change to existing functionality

Proposed functionality

I propose when utilization is full, i.e. there is nothing free left, the utilization bar would not show the same red as it shows for 90% or 99.9%.
Instead it could show a (slightly) different color, say brighter/darker red or purple.

Use case

Make it easy for human operator to distinguish from the utilization bar whether utilization is totally full 100%, or not totally full <100%.

Currently the operator cannot just scan the list of utilization bars for whether something is 100% full or almost full because the bar has the same color and may display too similar bar length for 99%/99.9% and 100%.

100% is a slightly special case since there is nothing free left inside, so indicate that to the operator for spotting it easily.

Database changes

None.

External dependencies

None.

Originally created by @bluikko on GitHub (Jan 5, 2022). ### NetBox version v3.1.4 ### Feature type Change to existing functionality ### Proposed functionality I propose when utilization is full, i.e. there is nothing free left, the utilization bar would not show the same red as it shows for 90% or 99.9%. Instead it could show a (slightly) different color, say brighter/darker red or purple. ### Use case Make it easy for human operator to distinguish from the utilization bar whether utilization is totally full 100%, or not totally full <100%. Currently the operator cannot just scan the list of utilization bars for whether something is 100% full or almost full because the bar has the same color and may display too similar bar length for 99%/99.9% and 100%. 100% is a slightly special case since there is nothing free left inside, so indicate that to the operator for spotting it easily. ### Database changes None. ### External dependencies None.
adam added the status: acceptedtype: feature labels 2025-12-29 19:33:46 +01:00
adam closed this issue 2025-12-29 19:33:46 +01:00
adam commented 2025-12-29 19:33:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 5, 2022):

The utilization_graph tag used to render these graphs currently supports warning (yellow) and danger (red) thresholds; these default to 75 and 90, respectively. It should be simple to extend this to include a special style/color for 100 values, although we might also need to look into rounding (e.g. 99.99% not being the same as 100%).

@jeremystretch commented on GitHub (Jan 5, 2022): The `utilization_graph` tag used to render these graphs currently supports warning (yellow) and danger (red) thresholds; these default to 75 and 90, respectively. It should be simple to extend this to include a special style/color for 100 values, although we might also need to look into rounding (e.g. 99.99% not being the same as 100%).
adam commented 2025-12-29 19:33:47 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 7, 2022):

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.

@github-actions[bot] commented on GitHub (Mar 7, 2022): 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 19:33:47 +01:00
Author
Owner
Copy Link

@bluikko commented on GitHub (Mar 31, 2022):

This works really well, thank you! Scrolling the prefix list now it is immediately obvious which ones are 100% used and it takes about 0% of cognitive capacity.

@bluikko commented on GitHub (Mar 31, 2022): This works really well, thank you! Scrolling the prefix list now it is immediately obvious which ones are 100% used and it takes about 0% of cognitive capacity.
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#5878
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?