Issue #10433 has been updated by Daniel Sauble. Status changed from Needs Decision to Accepted Assignee changed from Daniel Sauble to eric sorenson
I think this is completely reasonable. For a large infrastructure, this is a must, since the sheer quantity of resources in each change status renders filtering ineffective. If we allow users to filter on resource metaparameters, and give them the ability to save their filters, we shouldn't need to dedicate a separate view for this. ---------------------------------------- Feature #10433: Reporting change categories https://projects.puppetlabs.com/issues/10433#change-67176 Author: Matt Goebel Status: Accepted Priority: Normal Assignee: eric sorenson Category: Target version: Affected Puppet version: Keywords: Branch: I use the dashboard to monitor system changes. Some changes I care about, some are completely trivial and I don't really care to know about them. Simply reporting a system as "changed" makes it very difficult to sort out what's what. I would like to see a few change "categories" if you will that I could define per resource. So instead of just having changed on the dashboard you'd have something like changed - critial/normal(default)/trivial etc... User defined categories in addition to some default ones would be the ideal. This is slightly related to #7555 although no reporting is not what I'm asking for here. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
