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

CSV Export/Re-import of multiple interface cable traces #5736

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

Originally created by @maxzapp on GitHub (Dec 7, 2021).

NetBox version

v3.0.11

Feature type

New functionality

Proposed functionality

CSV Export of multiple cable traces.
Cable trace is a logical end to end patching information of two active interfaces over multipel hops passive of cables and patch panels.
Included information should be same as in the graphical cable trace view.
Selection options should be:
export all traces from all interfaces of a single device
export all traces from all interfaces of complete rack.

Use case

This helps admins to verify and correct offline their patching information without access to netbox wich is often the case on remote rooms, buildings, locations and sites.

Database changes

Mayb each cable trace needs a uniqe id to avoid double listing (trace A to B is the same as trace B to A)

External dependencies

unknown

Originally created by @maxzapp on GitHub (Dec 7, 2021). ### NetBox version v3.0.11 ### Feature type New functionality ### Proposed functionality CSV Export of multiple cable traces. Cable trace is a logical end to end patching information of two active interfaces over multipel hops passive of cables and patch panels. Included information should be same as in the graphical cable trace view. Selection options should be: export all traces from all interfaces of a single device export all traces from all interfaces of complete rack. ### Use case This helps admins to verify and correct offline their patching information without access to netbox wich is often the case on remote rooms, buildings, locations and sites. ### Database changes Mayb each cable trace needs a uniqe id to avoid double listing (trace A to B is the same as trace B to A) ### External dependencies unknown
adam added the type: featurestatus: revisions needed labels 2025-12-29 19:32:02 +01:00
adam closed this issue 2025-12-29 19:32:02 +01:00
adam commented 2025-12-29 19:32:02 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 7, 2021):

Please take some time to rewrite your feature request so that it clearly conveys what you're proposing. It's not at all clear from what you've written above what you're trying to accomplish.

@jeremystretch commented on GitHub (Dec 7, 2021): Please take some time to rewrite your feature request so that it clearly conveys what you're proposing. It's not at all clear from what you've written above what you're trying to accomplish.
adam commented 2025-12-29 19:32:03 +01:00
Author
Owner
Copy Link

@maxzapp commented on GitHub (Dec 9, 2021):

sorry english is not my native language, so i try my best.

@maxzapp commented on GitHub (Dec 9, 2021): sorry english is not my native language, so i try my best.
adam commented 2025-12-29 19:32:03 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 21, 2021):

There isn't a standardized way to export cable traces, as each can traverse an arbitrary number of nodes and links. It sounds like your use case would be best served by authoring a custom script that would cater to your specific workflow.

@jeremystretch commented on GitHub (Dec 21, 2021): There isn't a standardized way to export cable traces, as each can traverse an arbitrary number of nodes and links. It sounds like your use case would be best served by authoring a [custom script](https://netbox.readthedocs.io/en/stable/customization/custom-scripts/) that would cater to your specific workflow.
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 status: revisions needed 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#5736
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?