Power Utilization not fully calculated #10421

Closed
opened 2025-12-29 21:31:14 +01:00 by adam · 3 comments
Owner

Originally created by @craigmoscardini on GitHub (Oct 30, 2024).

NetBox version

4.0.9

Feature type

Change to existing functionality

Triage priority

N/A

Proposed functionality

Improve power calculations to traverse downstream devices to ensure power calculation per rack is accurate

See https://github.com/netbox-community/netbox/issues/17843#issue-2609237181 and https://github.com/netbox-community/netbox/issues/3377#issue-474826541

Use case

Current power utilisation adds little to no value as multiple downstream devices is an extremely common scenario which is not calculated correctly.

Database changes

Unknown

External dependencies

No response

Originally created by @craigmoscardini on GitHub (Oct 30, 2024). ### NetBox version 4.0.9 ### Feature type Change to existing functionality ### Triage priority N/A ### Proposed functionality Improve power calculations to traverse downstream devices to ensure power calculation per rack is accurate See https://github.com/netbox-community/netbox/issues/17843#issue-2609237181 and https://github.com/netbox-community/netbox/issues/3377#issue-474826541 ### Use case Current power utilisation adds little to no value as multiple downstream devices is an extremely common scenario which is not calculated correctly. ### Database changes Unknown ### External dependencies _No response_
adam closed this issue 2025-12-29 21:31:14 +01:00
Author
Owner

@246Tech commented on GitHub (Nov 4, 2024):

I have fallen into this problem also where from the pannel it does to a UPS then to a PDU then to the devices .
If i only have the UPS, or only the PDU the calculation works.

@246Tech commented on GitHub (Nov 4, 2024): I have fallen into this problem also where from the pannel it does to a UPS then to a PDU then to the devices . If i only have the UPS, or only the PDU the calculation works.
Author
Owner

@github-actions[bot] commented on GitHub (May 8, 2025):

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 (May 8, 2025): 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/main/CONTRIBUTING.md).
Author
Owner

@github-actions[bot] commented on GitHub (Jun 7, 2025):

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 (Jun 7, 2025): 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.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#10421