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

QOS fields within circuit details form. #1045

New Issue
Closed
opened 2025-12-29 16:28:16 +01:00 by adam · 4 comments
adam commented 2025-12-29 16:28:16 +01:00
Owner
Copy Link

Originally created by @PaulWesthead on GitHub (Jun 19, 2017).

Is it possible to make an addition to the circuits details tab allowing additions of feature information for a circuit?

The use case in the scenario I am looking at is our services have a CDR and associated QOS queue's. I am looking to add this as additional information against a circuit ID.

Cheers

Paul

Originally created by @PaulWesthead on GitHub (Jun 19, 2017). Is it possible to make an addition to the circuits details tab allowing additions of feature information for a circuit? The use case in the scenario I am looking at is our services have a CDR and associated QOS queue's. I am looking to add this as additional information against a circuit ID. Cheers Paul
adam closed this issue 2025-12-29 16:28:16 +01:00
adam commented 2025-12-29 16:28:16 +01:00
Author
Owner
Copy Link

@andreas1o commented on GitHub (Jun 19, 2017):

I would also like to so related circuits, ie one circuit depends on another.
Is that something that is doable ?

@andreas1o commented on GitHub (Jun 19, 2017): I would also like to so related circuits, ie one circuit depends on another. Is that something that is doable ?
adam commented 2025-12-29 16:28:17 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 19, 2017):

This feature request lacks sufficient detail to be actionable. Per the contributing guidelines:

When submitting a feature request on GitHub, be sure to include the following:

  • A detailed description of the proposed functionality
  • A use case for the feature; who would use it and what value it would add to NetBox
  • A rough description of changes necessary to the database schema (if applicable)
  • Any third-party libraries or other resources which would be involved

Please extend the request so that it meets all of these requirements. If no response is received within a week, this issue will be closed.

@jeremystretch commented on GitHub (Jun 19, 2017): This feature request lacks sufficient detail to be actionable. Per the [contributing guidelines](https://github.com/digitalocean/netbox/blob/develop/CONTRIBUTING.md): > When submitting a feature request on GitHub, be sure to include the following: > > * A detailed description of the proposed functionality > * A use case for the feature; who would use it and what value it would add to NetBox > * A rough description of changes necessary to the database schema (if applicable) > * Any third-party libraries or other resources which would be involved Please extend the request so that it meets all of these requirements. If no response is received within a week, this issue will be closed.
adam commented 2025-12-29 16:28:17 +01:00
Author
Owner
Copy Link

@PaulWesthead commented on GitHub (Jun 19, 2017):

Hi Jeremy,

I do apologise for not providing enough initial detail, I hope the below satisfies what you are after:

A detailed description of the proposed functionality

We make use of a national MPLS network provided by a third party. Within this network we are provided with a CDR (Committed Data Rate) of best effort bandwidth. As an additional service offering the service provider allows us to apply QOS (Quality of Service) Markings i.e EF,AF1-4 and BE. This is a billable item, however we are unable to establish what the provider is providing without trawling back through bills. It would be ideal if we could track what we have made provision for. We are currently using the comments field for tracking this for example: Circuit ABC12345 500Kbps of EF markings (For voice traffic)

A use case for the feature; who would use it and what value it would add to NetBox

This is just an additional database field (I think) within netbox and could be used for calculating total QOS markings required at the remote site end as well as the datacentre end. For example, EF should be used on an uncontended basis, so if we have 10 sites with 500Kbps EF access then the datacentre end would require 5000Kbps. This is an addition to the exiting circuit CDR capability.

A rough description of changes necessary to the database schema (if applicable)

N/A

Any third-party libraries or other resources which would be involved

N/A

I hope this helps.

Thanks

Paul

@PaulWesthead commented on GitHub (Jun 19, 2017): Hi Jeremy, I do apologise for not providing enough initial detail, I hope the below satisfies what you are after: > A detailed description of the proposed functionality We make use of a national MPLS network provided by a third party. Within this network we are provided with a CDR (Committed Data Rate) of best effort bandwidth. As an additional service offering the service provider allows us to apply QOS (Quality of Service) Markings i.e EF,AF1-4 and BE. This is a billable item, however we are unable to establish what the provider is providing without trawling back through bills. It would be ideal if we could track what we have made provision for. We are currently using the comments field for tracking this for example: Circuit ABC12345 500Kbps of EF markings (For voice traffic) > A use case for the feature; who would use it and what value it would add to NetBox This is just an additional database field (I think) within netbox and could be used for calculating total QOS markings required at the remote site end as well as the datacentre end. For example, EF should be used on an uncontended basis, so if we have 10 sites with 500Kbps EF access then the datacentre end would require 5000Kbps. This is an addition to the exiting circuit CDR capability. > A rough description of changes necessary to the database schema (if applicable) N/A > Any third-party libraries or other resources which would be involved N/A I hope this helps. Thanks Paul
adam commented 2025-12-29 16:28:17 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 23, 2017):

QOS markings get into configuration management territory, similar to prefix filters and firewall policies. This is a bit too far out of scope (and probably a bit esoteric) to add to the schema. However, you can easily create a custom field to track this data for individual circuits. Hopefully that's a workable solution for your use case.

@jeremystretch commented on GitHub (Jun 23, 2017): QOS markings get into configuration management territory, similar to prefix filters and firewall policies. This is a bit too far out of scope (and probably a bit esoteric) to add to the schema. However, you can easily create a [custom field](http://netbox.readthedocs.io/en/stable/data-model/extras/#custom-fields) to track this data for individual circuits. Hopefully that's a workable solution for your use case.
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
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#1045
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?