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!

Event Feed timescale expansion

Customers that would benefit:

Any customer who wants to view Event Feed information from more than 7 days ago

Problem being solved:

The inability to view event information from within Automate for more than the past 7 days

Ideal Outcome:

The ability to fully customize the timeframe for which event data is viewed

Minimum Acceptable:

The ability to at least select a 7 day period prior to the (current day - 6) that is currently displayed.

 

  • Daniel Bright
  • May 24 2019
  • Currently Declined
  • Attach files
  • Natalie Fisher commented
    13 Apr 05:16pm

    Thanks to all of our customers and customer facing teams that drive feature requests to make our product better.

    I know this is a feature that was requested almost a year ago and we still view this as an item that would be valuable and we will likely implement, at this time this is not something we will do in the short-term and will need to be prioritized against other larger initiatives. Thanks for your patience and understanding.

    ×

    Attachments Open full size

  • Guest commented
    10 Dec, 2019 05:06pm

    even application teams in my company are requesting at least a month of event data.

    ×

    Attachments Open full size

  • Daniel Bright commented
    17 Jun, 2019 12:16pm

    My customers in general want to have a 1-month history of client run and compliance data, and currently if they see a spike in compliance issues, say from 10 days ago, they want to be able to quickly and easily see what specific items on the chef-server might have changed 10 days ago to help them correlate the issue. I.E. if a new cookbook version was pushed to prod 10 days ago, and 10 days ago there was a spike in compliance failures, there might be some correlation.

    ×

    Attachments Open full size

  • Admin
    Mike Krasnow commented
    14 Jun, 2019 06:10pm

    You can pull historical data from the API. If that was better documented, would that be enough?

    I'd like to understand better what the problem is that the customer is trying to solve. How far back do we need to go? What are they looking for?

    ×

    Attachments Open full size

Related ideas