-
Notifications
You must be signed in to change notification settings - Fork 59
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
pipe
shall allow to export the node utilization report
#1628
Labels
goal/dorado ✨
kind/enhancement
New feature or request
state/has-doc
Issues that have documentation
state/verify
Issues that are already addressed and require validation
sys/cli
Issues related to the pipe cli
Milestone
Comments
Backport to |
ekazachkova
added a commit
that referenced
this issue
Dec 4, 2020
mzueva
pushed a commit
that referenced
this issue
Dec 7, 2020
mzueva
added
the
state/verify
Issues that are already addressed and require validation
label
Dec 7, 2020
ekazachkova
added a commit
that referenced
this issue
Dec 10, 2020
mzueva
pushed a commit
that referenced
this issue
Dec 10, 2020
mzueva
pushed a commit
that referenced
this issue
Dec 10, 2020
@sidoruka backported to |
Verified. Were tested:
|
Docs were updated via #1516. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
goal/dorado ✨
kind/enhancement
New feature or request
state/has-doc
Issues that have documentation
state/verify
Issues that are already addressed and require validation
sys/cli
Issues related to the pipe cli
Background
At the moment, Cloud Pipeline allows viewing the nodes utilization reports in the GUI. But in some cases, users would like to export this information for further usage in an automated manner.
Approach
--instance-id
and--run-id
options shall be specified. If a--run-id
is set - then the instance id shall be retrieved from the respective job. Both options cannot be set together.--from
/--to
- dates to generate the report:--to
is not set - use current date--from
is not set - use--to
minus 1 day--interval
- same periods list as we have in the GUI:--output
- where to place the resulting file. If not set - create it incwd
with the auto-generated name using the query parameters:<cluster_monitor_$RUN_ID/$INSTANCE_ID_$FROM_$TO_$INTERVAL.csv>
The text was updated successfully, but these errors were encountered: