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.

Sign up for GitHub

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

Jump to bottom

Depsolver Metrics Addition #1494

Open
sean-horn opened this issue Apr 25, 2018 · 0 comments
Open

Depsolver Metrics Addition #1494

sean-horn opened this issue Apr 25, 2018 · 0 comments
Labels
Aspect: Performance Works without negatively affecting the system running it. Triage: Try Reproducing Indicates that this issue needs to be reproduced. Type: Enhancement Adds new functionality.

Comments

@sean-horn
Copy link
Contributor

sean-horn commented Apr 25, 2018 •
edited
Loading

We should include monitoring of the current depsolver usage in the output at FQDN/_stats
We currently do little to no monitoring of depsolver activity.

We have more issues about depsolving than we would like with no insight into the depsolver workers' behavior.

Appropriate metrics would be

  • Current depsolver workers pool count (may exist now)
  • Current number of depsolver workers used from the pool (may exist now)
  • min/median/max depsolving times
  • client name + run_list and versions + depsolving total time for each chef-client connection

Expected Behavior

We have stats about depsolvers that allow us to pick out which chef-client connections are misbehaving and taking a long time to depsolve so that we can more rapidly address problem clients.

Current Behavior

No metrics available for depsolver workers

Environment

Modern Chef Servers, 12.0.x and above

Related: #36
@tas50 tas50 added Type: Enhancement Adds new functionality. Aspect: Scalability and removed enhancement labels Jan 4, 2019
@tas50 tas50 added Aspect: Performance Works without negatively affecting the system running it. and removed Aspect: Scalability labels Jan 28, 2019
@PrajaktaPurohit PrajaktaPurohit added the Triage: Try Reproducing Indicates that this issue needs to be reproduced. label Aug 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Aspect: Performance Works without negatively affecting the system running it. Triage: Try Reproducing Indicates that this issue needs to be reproduced. Type: Enhancement Adds new functionality.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tas50 @sean-horn @PrajaktaPurohit