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

Cable trace in cable view #7579

New Issue
Closed
opened 2025-12-29 20:25:39 +01:00 by adam · 7 comments
adam commented 2025-12-29 20:25:39 +01:00
Owner
Copy Link

Originally created by @CaptainBalou on GitHub (Jan 31, 2023).

NetBox version

v3.4.3

Feature type

Change to existing functionality

Proposed functionality

It would be awesome to have the possibility to click on tracing a cable while viewing the cable (e.g. https://localhost/dcim/cables/1/)

image

as well as on the list view

image

Use case

Being in the data center, seeing a cable without knowing whats connected would involve searching for the cable ID printed on the cable label. After finding it in Netbox it would be nice to see a trace icon image in the list overview as well as in the details page of each cable to be able to directly get a trace to each end without the need of click of one connected interface to click on trace there (see example screenshots above in the proposal).

Database changes

No response

External dependencies

No response

Originally created by @CaptainBalou on GitHub (Jan 31, 2023). ### NetBox version v3.4.3 ### Feature type Change to existing functionality ### Proposed functionality It would be awesome to have the possibility to click on tracing a cable while viewing the cable (e.g. https://localhost/dcim/cables/1/) ![image](https://user-images.githubusercontent.com/17015872/215703252-3cdb0b51-04e5-4ccb-8ddc-f1ab56fbded0.png) as well as on the list view ![image](https://user-images.githubusercontent.com/17015872/215703468-eeece04c-9102-41b2-be0d-daccb64159f7.png) ### Use case Being in the data center, seeing a cable without knowing whats connected would involve searching for the cable ID printed on the cable label. After finding it in Netbox it would be nice to see a trace icon ![image](https://user-images.githubusercontent.com/17015872/215700241-748e7062-4742-4f74-b49e-c5771be6146c.png) in the list overview as well as in the details page of each cable to be able to directly get a trace to each end without the need of click of one connected interface to click on trace there (see example screenshots above in the proposal). ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featuretopic: cabling labels 2025-12-29 20:25:39 +01:00
adam closed this issue 2025-12-29 20:25:39 +01:00
adam commented 2025-12-29 20:25:40 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 18, 2023):

I'll note that cable traces need to start from a specific termination point (rather than from the cable itself) to imbue a direction of the trace, but we can add trace buttons to the termination objects.

@jeremystretch commented on GitHub (Feb 18, 2023): I'll note that cable traces need to start from a specific termination point (rather than from the cable itself) to imbue a direction of the trace, but we can add trace buttons to the termination objects.
adam commented 2025-12-29 20:25:40 +01:00
Author
Owner
Copy Link

@PieterL75 commented on GitHub (Feb 28, 2023):

I was looking into this.. The only place that I can add the trace, is on the Cable page, on the interface (if shown).
image

As a cable can have multiple interfaces on each termination side, it is not possible to create a 'trace' button for the 'cable' or show it in the cable list.
Unless we assume that is the a_terminations[0] or b_terminations[0] exists, that we can start the trace from there..

@PieterL75 commented on GitHub (Feb 28, 2023): I was looking into this.. The only place that I can add the trace, is on the Cable page, on the interface (if shown). ![image](https://user-images.githubusercontent.com/74899468/221815450-256193f7-1b01-4970-a994-cd92ef189fbd.png) As a cable can have multiple interfaces on each termination side, it is not possible to create a 'trace' button for the 'cable' or show it in the cable list. Unless we assume that is the a_terminations[0] or b_terminations[0] exists, that we can start the trace from there..
adam commented 2025-12-29 20:25:41 +01:00
Author
Owner
Copy Link

@PieterL75 commented on GitHub (Feb 28, 2023):

2 options for the 'list' view :
image
either a button next to the termination or a dropdown with all possible traces of that cable.
The first one is easy, then I can decide in the python code of the interface is a 'interface/front/rear', other types are not traceable. The dropdown is more difficult (I think) as it there is no type of the termination/cable passed to the django template

@PieterL75 commented on GitHub (Feb 28, 2023): 2 options for the 'list' view : ![image](https://user-images.githubusercontent.com/74899468/221866739-cc5ca5bf-2811-4f09-95c7-543bed04dfc3.png) either a button next to the termination or a dropdown with all possible traces of that cable. The first one is easy, then I can decide in the python code of the interface is a 'interface/front/rear', other types are not traceable. The dropdown is more difficult (I think) as it there is no type of the termination/cable passed to the django template
adam commented 2025-12-29 20:25:41 +01:00
Author
Owner
Copy Link

@PieterL75 commented on GitHub (Mar 1, 2023):

I think I have something that works. See PR..
If we start the trace of any termination of that cable, we get the trace. You won't be able to trace from A-Z or Z-A, just the first valid iface is picked.
In the end, the result is that the cable is shown.

@PieterL75 commented on GitHub (Mar 1, 2023): I think I have something that works. See PR.. If we start the trace of any termination of that cable, we get the trace. You won't be able to trace from A-Z or Z-A, just the first valid iface is picked. In the end, the result is that the cable is shown.
adam commented 2025-12-29 20:25:41 +01:00
Author
Owner
Copy Link

@CaptainBalou commented on GitHub (Mar 2, 2023):

@jeremystretch @PieterL75

Hello,

I really appreciate that you guys are thinking about this directly. Thanks. @PieterL75 is even faster in changing the code then I had the time to look at the proposals. Awesome. :-)
Because the list is not very crowded I would prefer the icon directly in the list. But a drop-down would also be good. Both makes it easier for users to reach the trace with fewer clicks.

Kind regards
Marco

@CaptainBalou commented on GitHub (Mar 2, 2023): @jeremystretch @PieterL75 Hello, I really appreciate that you guys are thinking about this directly. Thanks. @PieterL75 is even faster in changing the code then I had the time to look at the proposals. Awesome. :-) Because the list is not very crowded I would prefer the icon directly in the list. But a drop-down would also be good. Both makes it easier for users to reach the trace with fewer clicks. Kind regards Marco
adam commented 2025-12-29 20:25:42 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 1, 2023):

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 (Jun 1, 2023): 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/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:25:42 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 2, 2023):

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 (Jul 2, 2023): 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.
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 topic: cabling 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#7579
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?