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

Create a Job Summary API #1340

Closed
dadgar opened this issue Jun 22, 2016 · 5 comments
Closed

Create a Job Summary API #1340

dadgar opened this issue Jun 22, 2016 · 5 comments
Labels
theme/api HTTP API and SDK issues type/enhancement

Comments

@dadgar
Copy link
Contributor

dadgar commented Jun 22, 2016

Have a Job Summary API that will list the number of allocations in the following state:

  • Pending
  • Starting
  • Running
  • Complete
  • Failed
@camerondavison
Copy link
Contributor

My ideal api (in keeping as similar look and feel as the existing api) would look something like

$ nomad status
<every job>
==> Job Summary
Pending   = 10
Starting  = 0
...

$ nomad status some-prefix
<every job matching that prefix>
==> Job Summary
...

$ nomad status some-exact-id
<current nomad status output>
==> Job Summary
...

also, it would be nice to add a param such as -machine for an output that is a little easier to parse with awk and grep and such.

@dadgar
Copy link
Contributor Author

dadgar commented Jun 22, 2016

What does the first output represent? The rolled up state of the whole cluster?

@camerondavison
Copy link
Contributor

Yes

On Wed, Jun 22, 2016, 2:25 PM Alex Dadgar notifications@github.com wrote:

What does the first output represent? The rolled up state of the whole
cluster?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#1340 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAKGBYm-ndFLYIn4mMdjEcRQKUTaCsnIks5qOYwJgaJpZM4I7_Lb
.

@dadgar
Copy link
Contributor Author

dadgar commented Jul 27, 2016

Fixed by #1455

@dadgar dadgar closed this as completed Jul 27, 2016
@github-actions
Copy link

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
theme/api HTTP API and SDK issues type/enhancement
Projects
None yet
Development

No branches or pull requests

2 participants