feat(asset): add utilization query #66
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TigranVardanyan
requested review from
CiprianAnton,
kkerezsi,
mure and
cameronwaterman
as code owners
|
@TigranVardanyan Can you integrate this with the PR that just went in to move the calibration forecast functionality into a separate plugin: #65 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request
🤨 Rationale
Added query to Asset datasource to visualize utilization data
👩💻 Implementation
Since in API there are no endpoints at the moment that return utilization data in a historical format, functions have been written to calculate them.
🧪 Testing
Data for verification was taken from the endpoint 'niapm/v1/query-asset-utilization'.
✅ Checklist