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

Meaning of the WaitingJobs and ScheduledJobs metrics? #129

Closed
edmund-huber opened this issue Mar 13, 2023 · 1 comment · Fixed by #130
Closed

Meaning of the WaitingJobs and ScheduledJobs metrics? #129

edmund-huber opened this issue Mar 13, 2023 · 1 comment · Fixed by #130

Comments

@edmund-huber
Copy link
Contributor

Neither in the README of this project, nor in the API docs https://buildkite.com/docs/apis/agent-api/metrics, do I find an explanation of what these different metrics mean. Most of the metrics are self-explanatory, but I'm still not clear about WaitingJobs and ScheduledJobs.

In my graphs, I only very occasionally see ScheduledJobs go over 0. Since I'm overprovisioned with agents, I suppose this means that ScheduledJobs is measuring how many jobs want to find a free agent but can't. Is this correct?

In my graphs, WaitingJobs is very often greater than 0. It often trends pretty closely with RunningJobs. My current best guess is that jobs are "waiting" when they have an agent to run on, but the git clone/checkout is still happening. Is that correct? What does WaitingJobs mean?

@edmund-huber
Copy link
Contributor Author

My current best guess is that jobs are "waiting" when they have an agent to run on, but the git clone/checkout is still happening.

I don't think this can be correct, because when I have high numbers of "waiting jobs", the number of "busy agents" has not increased.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant