Sorry for the long delay, had my head down on some other issues. Reply below.
On Jan 10, 2012, at 10:55 AM, Daniel Pittman wrote: > Yes. It sounds like the current storage of reports isn't going to > work well for you, at least if you want to retain history. This is > absolutely unfortunate, and is one of the serious shortfalls we are > aware of around the Dashboard and StoreConfigs databases. We are > working on improving these, but there isn't anything presently public > available. My main concern here is that we're keeping a large amount of data twice. We have the report file, and then we have all of the same content in the database. I think that it should be documented: 1. What does keeping the reports around give you? 2. What does keeping the database reports around give you? If I am right, we could stop storing the reports for as long if we can browse them in the dashboard interface, right? Or is there some loss of functionality by discarding reports after just a few days? -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.