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

Add "switch utilization" - just like "rack utilization" #6844

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

Originally created by @rtxtmardesen on GitHub (Aug 21, 2022).

NetBox version

v3.2.5

Feature type

New functionality

Proposed functionality

Just like the "Rack Utilization" information point, it would be great to see a switch and see how many ports are taken up. Beyond that, it would also be great to see (as an aggregate) the number of open ports that all the switches have in a specific rack. Maybe even site, location, etc.

Use case

As a company who has netbox fully implemented, I am deciding which location/site to place a large unracked device that consumes 10+ ports on a switch. being able to see which lab has the most available ports would help solve this situation.

Also, "do I need to purchase another switch?" questions can be solved sooner.

Database changes

I know this would change some schema a little bit, unsure the finite details.

External dependencies

No response

Originally created by @rtxtmardesen on GitHub (Aug 21, 2022). ### NetBox version v3.2.5 ### Feature type New functionality ### Proposed functionality Just like the "Rack Utilization" information point, it would be great to see a switch and see how many ports are taken up. Beyond that, it would also be great to see (as an aggregate) the number of open ports that all the switches have in a specific rack. Maybe even site, location, etc. ### Use case As a company who has netbox fully implemented, I am deciding which location/site to place a large unracked device that consumes 10+ ports on a switch. being able to see which lab has the most available ports would help solve this situation. Also, "do I need to purchase another switch?" questions can be solved sooner. ### Database changes I know this would change some schema a little bit, unsure the finite details. ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:45:59 +01:00
adam closed this issue 2025-12-29 19:45:59 +01:00
adam commented 2025-12-29 19:46:02 +01:00
Author
Owner
Copy Link

@DorianBourgeoisat commented on GitHub (Aug 21, 2022):

At first glance, I think this can be done relatively easily by :

  • Having an "interface utilization" for devices
  • Having a toggle for use in aggregate for each device (to distinguish switch-like devices from others)
@DorianBourgeoisat commented on GitHub (Aug 21, 2022): At first glance, I think this can be done _relatively_ easily by : - Having an "interface utilization" for devices - Having a toggle for use in aggregate for each device (to distinguish switch-like devices from others)
adam commented 2025-12-29 19:46:02 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 22, 2022):

This doesn't seem practical IMO, for several reasons:

  1. It's not typical that you decide where to put a device based on how many interfaces are available on a switch.
  2. Your proposed implementation completely ignores interface types.
  3. Utilization would be reported for every device. Devices with a single connected interface would report 100% utilization.
@jeremystretch commented on GitHub (Aug 22, 2022): This doesn't seem practical IMO, for several reasons: 1. It's not typical that you decide where to put a device based on how many interfaces are available on a switch. 2. Your proposed implementation completely ignores interface types. 3. Utilization would be reported for _every_ device. Devices with a single connected interface would report 100% utilization.
adam commented 2025-12-29 19:46:02 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 31, 2022):

I'm sorry but this very much seems like it would deliver more confusion than value, so I'm going to decline the proposal. If you're interested in capturing this type of information, consider writing a report that can be easily tailored to your specific needs.

@jeremystretch commented on GitHub (Aug 31, 2022): I'm sorry but this very much seems like it would deliver more confusion than value, so I'm going to decline the proposal. If you're interested in capturing this type of information, consider writing a [report](https://docs.netbox.dev/en/stable/customization/reports/) that can be easily tailored to your specific needs.
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#6844
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?