Chef Ideas

We believe that the best way to build software is to do it in close collaboration with the people who use it. We invite you to submit your ideas using the form below. Please be sure to include the problem for which you are solving and the benefits of implementing the idea.

We do our best to implement as many Ideas as we can. Our Product team will evaluate all submitted ideas in a timely manner and will disposition each into one of the following categories: will integrate into the product roadmap, further research is needed, unlikely to implement.

Thanks for collaborating with us!

API for the time taken per request and number of requests to elasticsearch.

Create an API that helps understand the latency of chef infra server with its external connections like elasticsearch and postgres.

In recent support calls, it was found very difficult to diagnose if the slowness observed was due to chef-server or elastic-search or the latency between the two.

Having some instrumentation around monitoring the system to detect slowness would be very helpful in these scenarios.

It could be implemented with some counters (in Prometheus if possible)

1) the number of requests to Elasticsearch

2) time taken per request

3) request success and failure counts

  • Guest
  • Oct 11 2019
  • Currently Declined
  • Attach files
  • Mark Anderson commented
    31 Jan, 2020 09:24pm

    As a note, just had another customer call where this kind of statistic would have been very useful. 

  • Joshua O'Brien commented
    30 Oct, 2019 08:13pm

    Adding to Chef Infra epics board

  • Mark Anderson commented
    15 Oct, 2019 07:04pm

    Having done a lot of chef-server diagnostics in support calls I would emphasize how useful this would be. Being able to partition the problem to 'chef-server' and upstream,  or downstream to database/elasticsearch would greatly speed debugging. Debugging either path can be quite time consuming, and if you pick the wrong one you have lost a lot of time barking up the wrong tree. It would be applicable to to any multi-node configuration including tiered, chef-backend, BYODB, and various cloud based options.