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!

Automate 2 retention should be limited by default

The following full config should be active upon installation of an Automate 2 system, but with all `older_than_days` values set to 14 days or less. https://automate.chef.io/docs/data-lifecycle/

This restriction will help prevent regular out of disk space failures a week or a month after a customer installs the system.

If a customer would like to increase the retention period, they can do so, noting the space available for elasticsearch storage.

  • Guest
  • Jan 27 2020
  • Under Consideration
  • Attach files
  • Richard Nixon commented
    5 Mar 12:45am

    I also like the evasive manouvers that we had in A1 which kicked in on low disk space

  • Richard Nixon commented
    5 Mar 12:44am

    This would save so many people.

  • Brian Schwegmann commented
    25 Feb 12:48am

    We had another customer today that was surprised that unlimited data retention is the default.  It caused a sev1 outage and they assembled a team to mitigate the issue over the course of a couple hours.  People expect conservative defaults and they'll be happier with the product if it doesn't fail unexpectedly due to easily-preventable issues.

  • Shaun Mouton commented
    4 Feb 05:55pm

    In my interactions, customers have been surprised that we don't limit retention by default. We should do so, and use a notification banner to remind admins to check their retention settings. Notification banners are tight.

  • Chris Lavery commented
    4 Feb 05:53pm

    This is smart, like setting limits on other resources - men,  processes/connections. makes sense.