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!

View Infrastructure by unique errors

When new cookbook code is released and introduces problems in one or more environments, it would be helpful to know if the multiple of failing infrastructure is happening for the same reasons or different reasons. Right now, to view errors you have to click through each server individually. It makes it difficult to grasp the scope of a particular issue across the fleet of servers. Gathering this data is helpful though when writing up defects / issue tickets to track the problem and the resolution.


It would be great if we could introduce a new view for Infrastructure where instead of showing nodes, you saw a list of unique error messages and the number of servers impacted by that error. Then you can drill into each error to view the list of nodes impacted.


There is an API endpoint for this: https://docs.chef.io/automate/api/#operation/ConfigMgmt_GetErrors

This is incredibly helpful. I've been thinking about this feature for a while and only recently discovered the API for this today, so that's great. However it would be good through this API to also see the nodes for those errors in an array.


Not everyone is going to use the API, so it would be good to expose this to other users through the Automate UI as well.

  • Keith Walters
  • Nov 12 2021
  • Under Consideration
  • Attach files
  • Keith Walters commented
    4 May 11:56am

    Hi Ankur - I just saw the update to this. Yes I am available to speak with the UX team if they want.

  • Austin Culter commented
    22 Dec, 2021 07:55am

    I would like to second this idea. I think it would be great if the "Infrastructure/Client Runs" view (when filtered on 'Failed nodes'; i.e. `infrastructure/client-runs?status=failure`) had an optional header column that could be added for "Failed Cookbook" (or something) which would allow user to see which cookbook caused the Chef run failure. This would also allow for the user to sort/filter on this column and get a high-level view of what cookbook is failing.

  • Admin
    Ankur Mundhra commented
    17 Dec, 2021 07:58am

    Thanks for raising this Keith. I am adding our UX team to have a look at this. They may reach out to you for an interview session at an appropriate time. Will you be fine with it? For the time being I am declining it and will relook once UX team meets you and gives a guidance on this.