-
Notifications
You must be signed in to change notification settings - Fork 116
Add command for task metrics #923
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
Conversation
62f5e9e
to
e24d82a
Compare
cli/dcoscli/task/main.py
Outdated
""" | ||
|
||
master = mesos.get_master() | ||
slave_id = master.task(task_id)['slave_id'] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what if there are no slaves?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've added a guard for this, but I don't think a Mesos task object can ever not have a slave_id field.
Looks great. Is there a structure to the tags or can they be anything? |
Tags are arbitrary stringified key, value pairs. |
b24cd2f
to
187e75e
Compare
1d5b4d2
to
cdcbf82
Compare
mesosphere-backup/dcos-metrics#77 updated various keys for the task metrics API.
Add some sugar to avoid constant null-checks for datapoint values.
Integration tests require a one-minute pause and hence are not practicable.
be34148
to
ee237b8
Compare
The task metrics collector runs every minute, meaning that it did not reliably provide data to the integration tests. This could be fixed by adding a force-collection endpoint to tasks, but in the meantime these tests have been replaced with unit test.
This PR adds the
dcos task metrics
command.Components:
dcos task metrics details
/app
endpointdcos task metrics summary
dcos task metrics details
Example usage: