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

Display utilization of container prefixes based on child prefixes rather than IPs #1059

New Issue
Closed
opened 2025-12-29 16:28:23 +01:00 by adam · 0 comments
adam commented 2025-12-29 16:28:23 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Jun 26, 2017).

Issue type: Feature request

This idea was raised on the NetBox mailing list. Currently, prefix utilization is displayed as the percentage of consumed child IPs within it, regardless of the prefix's role. This doesn't make sense for container prefixes, which should have their utilization calculated in the same manner as aggregates: sum the space utilized by child prefixes and display it as a percentage relative to the parent prefix's size.

For example, a container prefix of 192.168.0.0/24 holding prefixes 192.168.0.0/26 and 192.168.0.64/26 should be considered 50% utilized, regardless of how many IP addresses have been created within it.

Originally created by @jeremystretch on GitHub (Jun 26, 2017). ### Issue type: Feature request This idea was raised [on the NetBox mailing list](https://groups.google.com/forum/#!topic/netbox-discuss/kgdH9n4G7dE). Currently, prefix utilization is displayed as the percentage of consumed child IPs within it, regardless of the prefix's role. This doesn't make sense for container prefixes, which should have their utilization calculated in the same manner as aggregates: sum the space utilized by child prefixes and display it as a percentage relative to the parent prefix's size. For example, a container prefix of 192.168.0.0/24 holding prefixes 192.168.0.0/26 and 192.168.0.64/26 should be considered 50% utilized, regardless of how many IP addresses have been created within it.
adam added the type: feature label 2025-12-29 16:28:23 +01:00
adam closed this issue 2025-12-29 16:28:23 +01:00
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 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#1059
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?