-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add formatted speed column to interface lists #13033
Labels
status: accepted
This issue has been accepted for implementation
type: feature
Introduction of new functionality to the application
Comments
Just to reiterate, this would introduce a new column, leaving the current column in place. The existing column works better for programmatic consumption; the new column better serves human readability. |
That is correct. I can take this if it's OK, as I already have the modifications made locally. |
matejv
added a commit
to matejv/netbox
that referenced
this issue
Jul 26, 2023
jeremystretch
pushed a commit
that referenced
this issue
Aug 2, 2023
jeremystretch
added a commit
that referenced
this issue
Aug 4, 2023
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
status: accepted
This issue has been accepted for implementation
type: feature
Introduction of new functionality to the application
NetBox version
v3.5.4
Feature type
New functionality
Proposed functionality
I propose adding a new column
Speed
toInterfaceTable
that would show interface speed but formatted the same way it is shown on interface details view. This column would be added in addition of existing columnSpeed (kbps)
.It would not be shown by default. Users could choose the column to be shown to show speed ether in kbps as now or shown formatted as 10 Gbps...
Use case
Currently it is difficult to determine if a speed is set to 1G, 10G or 100G without carefully counting if there are 6, 7 or 8 zeroes after 1.
With this change:
Database changes
None
External dependencies
None
The text was updated successfully, but these errors were encountered: