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

Bring back power feed utilisation graph to rack view #8964

New Issue
Closed
opened 2025-12-29 20:43:25 +01:00 by adam · 6 comments
adam commented 2025-12-29 20:43:25 +01:00
Owner
Copy Link

Originally created by @cpmills1975 on GitHub (Dec 13, 2023).

NetBox version

v3.6.6

Feature type

Change to existing functionality

Proposed functionality

The rack view used to show power feeds in a panel complete with a utilisation graph for each individual feed. While the overall power capacity is still shown, since the removal of this panel it is difficult to see whether the power utilisation is unbalanced between feeds in a rack.

I'd like to propose that the utilisation graph is made available in the power feeds list view. This would be included by default when viewing the filtered power feeds list reached through the 'related objects' link on the rack view.

Use case

I have a custom script which retrieves live(ish) power consumption statistics from my power management system and populates the power allocation field in the connected power ports. This information informs the power feed utilisation and allows me to see whether individual PDUs in a rack are balanced. More importantly, seeing the individual utilisation helps me ensure I'm not overloading one feed while under loading another - at present all I'd see is that the power availability on the rack is safely within parameters.

Database changes

None

External dependencies

None

Originally created by @cpmills1975 on GitHub (Dec 13, 2023). ### NetBox version v3.6.6 ### Feature type Change to existing functionality ### Proposed functionality The rack view used to show power feeds in a panel complete with a utilisation graph for each individual feed. While the overall power capacity is still shown, since the removal of this panel it is difficult to see whether the power utilisation is unbalanced between feeds in a rack. I'd like to propose that the utilisation graph is made available in the power feeds list view. This would be included by default when viewing the filtered power feeds list reached through the 'related objects' link on the rack view. ### Use case I have a custom script which retrieves live(ish) power consumption statistics from my power management system and populates the power allocation field in the connected power ports. This information informs the power feed utilisation and allows me to see whether individual PDUs in a rack are balanced. More importantly, seeing the individual utilisation helps me ensure I'm not overloading one feed while under loading another - at present all I'd see is that the power availability on the rack is safely within parameters. ### Database changes None ### External dependencies None
adam added the type: featurestatus: needs ownerpending closurecomplexity: medium labels 2025-12-29 20:43:25 +01:00
adam closed this issue 2025-12-29 20:43:25 +01:00
adam commented 2025-12-29 20:43:26 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 13, 2024):

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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Mar 13, 2024): 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. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:43:26 +01:00
Author
Owner
Copy Link

@RichZad commented on GitHub (Apr 19, 2024):

This function existed in 3.2.9 . Why was it removed?
This is critical to managing a robust data center operation.

@RichZad commented on GitHub (Apr 19, 2024): This function existed in 3.2.9 . Why was it removed? This is critical to managing a robust data center operation.
adam commented 2025-12-29 20:43:26 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (May 6, 2024):

@cpmills1975 @RichZad If I work on this could either of you do some tests / provide some feedback on it to help make sure it is working correctly?

@arthanson commented on GitHub (May 6, 2024): @cpmills1975 @RichZad If I work on this could either of you do some tests / provide some feedback on it to help make sure it is working correctly?
adam commented 2025-12-29 20:43:26 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 6, 2024):

Why was it removed?

IIRC there were several issues with utilization being reported inaccurately.

@jeremystretch commented on GitHub (May 6, 2024): > Why was it removed? IIRC there were several issues with utilization being reported inaccurately.
adam commented 2025-12-29 20:43:27 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 22, 2024):

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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Aug 22, 2024): 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. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:43:27 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 21, 2024):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Sep 21, 2024): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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: medium pending closure status: needs owner 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#8964
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?