On Mon, Aug 26, 2013 at 10:48 AM, Dustin J. Mitchell <[email protected]>wrote:
> The current situation is that master monitoring basically consists of > a no-op HTTP request. We'd like to get to a point where it includes > live status of the master. It makes sense for that live status to > include among other things some manually-flippable "in_service?" kind > of switch. > > Yeah, the current /<env>/status endpoint isn't very useful. > My understanding of the ARM is that it gets us a small step closer to > the latter, with a small code change. I think it makes a lot of sense > in that light, although it is perhaps not very ambitious for an ARM. > > I'd like to get it more useful, but I think need to have a clearer definition of what the "status of the master" means. If it is just the static content, then I see no point in it. So what might the master track in order to have a meaningful status page available? Since the status URL currently is /<env>/status/<unused key> it could be at a minimum if the environment exists by doing a stat of the manifest file for that environment. The key might be usable as something, but I'm drawing a blank on that right now. Because puppet works in a pre-fork model normally any given worker doesn't automatically have access to a global view of the whole master. It would need some way of communicating and collating information between the different workers. Since puppet is a Rack app, some of the Rack monitoring tools, might also fill this niche already. It may be a exercise in either documenting how to use them or giving puppet a few callbacks to send data to them. * http://www.sourcepole.com/2010/1/19/rack-monitor * https://www.ruby-toolbox.com/projects/metriks > Dustin > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/puppet-dev. > For more options, visit https://groups.google.com/groups/opt_out. > -- Andrew Parker [email protected] Freenode: zaphod42 Twitter: @aparker42 Software Developer -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-dev. For more options, visit https://groups.google.com/groups/opt_out.
