hello, ----- Original Message -----
> On Mon, Dec 20, 2010 at 3:26 AM, Brice Figureau > <[email protected]> wrote: > > On 20/12/10 05:32, [email protected] wrote: > > I'm not entirely clear how we could do this effectively with our > common deployment pattern of multiple daemons behind > Apache/nginx/pound, but I've found this sort of model far more useful > than just having debug logging in the past, and there are wider > benefits like being able to scrape this data more easily than parsing > syslog. > > I'm not really fond of the process name hack, but I'm not sure I have > a better suggestion either, so I'm echoing Brice's call for more input > from the community. > Me neither, I've never had cause to try to figure out what my master does at a specific point they tend to work well. that being said I dont dispute and wouldnt want to prevent someone from getting to that information if they needed it. I'd like to see a very simple plugin framework get written that gets called when instrumentation is needed, then we can have one that does the ps thing and one that lets say emit events over middleware to think of two extremes. I'd very much like to see that. -- 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.
