On 20/12/10 05:32, [email protected] wrote: > Hi Brice, > > This really just seems like eye candy to me for those who run top and > not really useful to anyone who wants to know "Why was my puppet > master slow at 3am this morning?".
I never pretended this patch would solve this issue :) This is a first step toward a broader solution that I hope can cover this use case. > How about asynchronously & > semantically logging it somewhere to a file or syslog so that those > who want to know can fire up Dashboard/Splunk/perl/python/ruby/awk on > the logs and find the answers. Compilation time and various other information are already logged, if you think there are some missing information, please let us know and we'll add more logs. But I think we need something more powerful and fine-grained, that could capture different metrics than only time spent doing something. Ultimately I'd like to offer a framework that can capture elapsed time, count, cpu time, memory, per probe. What is not clear at this stage is how to get access to those metrics, how long to keep them, how to aggregate them, where probes should be places, and so on... If anyone has any good ideas about these subjects (especially what scenario should be handled), that would be terriffic. Thanks, -- Brice Figureau My Blog: http://www.masterzen.fr/ -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev?hl=en.
