Add aggregated upstream power load tracking for power distribution devices #173

New Issue

MrUnknownDE · 2026-04-05T16:22:39+02:00

MrUnknownDE commented

2026-04-05 16:22:39 +02:00

Originally created by @powerscooter on 3/11/2026

NetBox version

v4.5.2

Feature type

Data model extension

Proposed functionality

Currently, NetBox allows modeling of power connections between devices (e.g., power panels, PDUs, and connected equipment). However, there is no built-in mechanism to visualize or calculate the aggregated load on an upstream power distribution device.

In our environment we have the following scenario:
• A power distribution unit / breaker panel provides 3 phases with 70A each.
• Multiple PDU strips are connected to this distributor.
• Each PDU outlet is rated for 16A and feeds individual devices.
• NetBox can model the connections between the PDUs and the devices, but it does not show the total load on the upstream distributor.

This makes it difficult to determine whether the main distributor or phase capacity is approaching its limit, even though the individual downstream loads are modeled.

Expected behavior / proposed feature:

NetBox should provide a way to:
1. Aggregate power load upstream
• Calculate the total current draw of devices connected through PDUs.
• Propagate this load upstream to the connected power distribution device.
2. Phase-aware load calculation
• Allow tracking of load per phase (L1/L2/L3).
• Display the total consumption vs. available capacity (e.g., 45A / 70A).
3. Capacity visualization
• Show utilization of upstream power devices, such as:
• Percentage usage
• Remaining capacity
• Optional warning thresholds.
4. Hierarchical power chain visibility
• Example chain:
Power Distributor (3x70A)
↓
PDU Strip (16A outlets)
↓
Servers / Devices

Use case

In datacenter environments, operators need to understand real load on upstream power infrastructure, not only the capacity of individual outlets. Without aggregated load tracking, capacity planning and safe deployment of additional equipment is difficult.

Benefits:
• Better power capacity planning
• Avoid overloading power distributors or phases
• Improved datacenter infrastructure visibility
• Aligns NetBox more closely with real-world power distribution modeling

Database changes

No response

External dependencies

No response

*Originally created by @powerscooter on 3/11/2026* ### NetBox version v4.5.2 ### Feature type Data model extension ### Proposed functionality Currently, NetBox allows modeling of power connections between devices (e.g., power panels, PDUs, and connected equipment). However, there is no built-in mechanism to visualize or calculate the aggregated load on an upstream power distribution device. In our environment we have the following scenario: • A power distribution unit / breaker panel provides 3 phases with 70A each. • Multiple PDU strips are connected to this distributor. • Each PDU outlet is rated for 16A and feeds individual devices. • NetBox can model the connections between the PDUs and the devices, but it does not show the total load on the upstream distributor. This makes it difficult to determine whether the main distributor or phase capacity is approaching its limit, even though the individual downstream loads are modeled. Expected behavior / proposed feature: NetBox should provide a way to: 1. Aggregate power load upstream • Calculate the total current draw of devices connected through PDUs. • Propagate this load upstream to the connected power distribution device. 2. Phase-aware load calculation • Allow tracking of load per phase (L1/L2/L3). • Display the total consumption vs. available capacity (e.g., 45A / 70A). 3. Capacity visualization • Show utilization of upstream power devices, such as: • Percentage usage • Remaining capacity • Optional warning thresholds. 4. Hierarchical power chain visibility • Example chain: Power Distributor (3x70A) ↓ PDU Strip (16A outlets) ↓ Servers / Devices ### Use case In datacenter environments, operators need to understand real load on upstream power infrastructure, not only the capacity of individual outlets. Without aggregated load tracking, capacity planning and safe deployment of additional equipment is difficult. Benefits: • Better power capacity planning • Avoid overloading power distributors or phases • Improved datacenter infrastructure visibility • Aligns NetBox more closely with real-world power distribution modeling ### Database changes _No response_ ### External dependencies _No response_

MrUnknownDE closed this issue

2026-04-05 16:22:39 +02:00

Sign in to join this conversation.

Branches Tags

main

21455-sql-indexes-audit

21357-register-model-actions

feature

20924-plugin-ui-components

21766-improve-test-coverage-for-sortable-table-columns

21157-export-template-public-models

21025-pre-render-config-contexts

21364-swagger

feature-ip-prefix-link

20911-dropdown-3

fix_module_substitution

21160-filterset

20911-dropdown-2

20044-elevation-stuck-lightmode

7604-filter-modifiers-v3

20660-script-load

19724-graphql

14884-script

19720-macaddress-interface-generic-relation

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

No Label netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/netbox#173