Skip to content
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 ability to read "Allocated Resources" for clusters over API #12596

Closed
stavr666 opened this issue May 12, 2023 · 4 comments · Fixed by #17956
Closed

Add ability to read "Allocated Resources" for clusters over API #12596

stavr666 opened this issue May 12, 2023 · 4 comments · Fixed by #17956
Assignees
Labels
complexity: medium Requires a substantial but not unusual amount of effort to implement netbox status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Milestone

Comments

@stavr666
Copy link

stavr666 commented May 12, 2023

NetBox version

v3.5.1

Feature type

Change to existing functionality

Proposed functionality

Return calculated "Allocated Resources" values to API endpoint.

If values stored in DB, add them to endpoints:

  • /api/virtualization/clusters/
  • /api/virtualization/clusters/{$id}/

Example in current UI:
image

Returned by API:
image

Example of expected output from same datapoint:
image

Database changes, new views or API endpoints - NOT REQUIRED afaik

Use case

Availability to fast-read actual values, without GraphQL or pipelining several API queries.

Target scenarios:

  • Resource saturation monitoring per cluster (target values defined either externally or in custom fields).
  • Raw resource cost approximation for cloud tenants/projects.

Database changes

No response

External dependencies

No response

@stavr666 stavr666 added the type: feature Introduction of new functionality to the application label May 12, 2023
@jeremystretch
Copy link
Member

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@jeremystretch jeremystretch added the status: revisions needed This issue requires additional information to be actionable label May 15, 2023
@stavr666
Copy link
Author

stavr666 commented May 16, 2023

@jeremystretch

thorough description of the proposed functionality

Example added

detailed use case justifying its implementation

It's was justified, as I far as I can. I just wanna directly use data, that already exists in Netbox UI, in our monitoring and reporting solutions, without external resource calculation for each cluster.

P.S. Can add similar example for "clusters" datapoint (without id), if needed.

@github-actions
Copy link
Contributor

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 github-actions bot added the pending closure Requires immediate attention to avoid being closed for inactivity label Aug 15, 2023
@abhi1693 abhi1693 added status: under review Further discussion is needed to determine this issue's scope and/or implementation and removed status: revisions needed This issue requires additional information to be actionable pending closure Requires immediate attention to avoid being closed for inactivity labels Aug 15, 2023
Copy link
Contributor

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 github-actions bot added the pending closure Requires immediate attention to avoid being closed for inactivity label Nov 14, 2023
@jeremystretch jeremystretch added needs milestone Awaiting prioritization for inclusion with a future NetBox release and removed status: under review Further discussion is needed to determine this issue's scope and/or implementation pending closure Requires immediate attention to avoid being closed for inactivity labels Dec 5, 2023
@jeremystretch jeremystretch added status: backlog Awaiting selection for work complexity: medium Requires a substantial but not unusual amount of effort to implement labels May 21, 2024
@jeremystretch jeremystretch added this to the v4.2 milestone Sep 26, 2024
@jeremystretch jeremystretch removed the needs milestone Awaiting prioritization for inclusion with a future NetBox release label Sep 26, 2024
@jeremystretch jeremystretch added v4.2 and removed v4.2 labels Oct 18, 2024
@jeremystretch jeremystretch added the netbox label Nov 1, 2024 — with Linear
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: backlog Awaiting selection for work labels Nov 14, 2024
@jeremystretch jeremystretch linked a pull request Nov 14, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity: medium Requires a substantial but not unusual amount of effort to implement netbox status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants