starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 22:03:32 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Add support to query device/interface endpoints for circuits #10520

New Issue
Open
opened 2025-12-29 21:32:33 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:32:33 +01:00
Owner
Copy Link

Originally created by @dmulyalin on GitHub (Nov 28, 2024).

NetBox version

v4.1.7

Feature type

New functionality

Triage priority

N/A

Proposed functionality

Add support to query over REST and GraphQL API devices and interface endpoints connected by this circuit

Currently to retrieve information on what devices and interfaces given circuit connects we have to query circuit terminations and from there send REST API request to trace the path for one of the interfaces circuit termination connected to. This is because circuits can be connected to rear-ports of patch panels and not to device interfaces directly, moreover, we can have multiple circuits connected together, as a result for big number of circuits (hundreds) it takes unreasonable amount of time to retrieve information on devices and interface that those circuits connect.

Use case

To provide applications using Netbox API with a way to efficiently query Netbox to retrieve information on devices and interfaces circuits are connecting.

Database changes

No response

External dependencies

No response

Originally created by @dmulyalin on GitHub (Nov 28, 2024). ### NetBox version v4.1.7 ### Feature type New functionality ### Triage priority N/A ### Proposed functionality Add support to query over REST and GraphQL API devices and interface endpoints connected by this circuit Currently to retrieve information on what devices and interfaces given circuit connects we have to query circuit terminations and from there send REST API request to trace the path for one of the interfaces circuit termination connected to. This is because circuits can be connected to rear-ports of patch panels and not to device interfaces directly, moreover, we can have multiple circuits connected together, as a result for big number of circuits (hundreds) it takes unreasonable amount of time to retrieve information on devices and interface that those circuits connect. ### Use case To provide applications using Netbox API with a way to efficiently query Netbox to retrieve information on devices and interfaces circuits are connecting. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurenetboxneeds milestonestatus: backlogcomplexity: high labels 2025-12-29 21:32:33 +01:00
adam commented 2025-12-29 21:32:34 +01:00
Author
Owner
Copy Link

@dmulyalin commented on GitHub (Apr 9, 2025):

In addition to having an ability to query endpoints, it would be beneficial to display circuit endpoints i.e. device and port under the main circuit view instead of making users to trace the circuit every time they need this piece of information.

@dmulyalin commented on GitHub (Apr 9, 2025): In addition to having an ability to query endpoints, it would be beneficial to display circuit endpoints i.e. device and port under the main circuit view instead of making users to trace the circuit every time they need this piece of information.
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 complexity: high needs milestone netbox status: backlog 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#10520
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?