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!

Add ability to filter by Cookbook for Node Detail view in Infrastructure

When looking at a Node in the Infrastructure view of Chef Automate, users are presented the options to filter by resource actions (all, success, failure). For nodes that run a number of different cookbooks with multiple resources, it can be burdensome to render via the web UI only the resource actions that happened for a specific cookbook.

When nodes run 10s or hundreds of resources that span multiple cookbooks, it is time consuming to click through the pagination of all resource executions.

Ideal scenario would be to add the ability to filter by a specific cookbook for the results view on the Node detail page.

  • Collin McNeese
  • Jul 27 2021
  • Currently Declined
  • Attach files
  • Guest commented
    3 Sep, 2021 02:56pm

    I would also like to have a way to filter through all of the resources - we often have 400+ resources in a run and it's very hard to find specific ones. Filtering by cookbook would be helpful, along with filtering by resource type (e.g. log to find if a message was logged) or even a plain old search, i.e. find any resources containing the text datadog (could be in the resource name, the cookbook, the diff of a file that was created, etc.).

  • +1