Logging api

Reviewers:  @bernerdschaefer, @peterbourgon 

First pass at the internals of the logging API.  This is two layers thick.  There is a RingBuffer for log messages, and on top of this is a data structure that implements storage for and operations for each container.  (The RingBuffer probably should have been a separate submit.)

The next piece to be worked on will be the HTTP logging interface.
Erg.  Thought I'd done that. (Just installed your hooks to prevent this in
the future.)


On Wed, Jul 30, 2014 at 5:53 PM, Bernerd Schaefer <notifications@github.com>
wrote:

> In harpoon-agent/api.go:
>
> > @@ -234,6 +236,53 @@ func isStreamAccept(accept string) bool {
> >  	return false
> >  }
> >
> > +func (a *api) handleLog(w http.ResponseWriter, r *http.Request) {
> > +	e := json.NewEncoder(w)
> > +
> > +	e.Encode(a.registry.Instances().EventBody())
> > +
> > +	var (
> > +		id = r.URL.Query().Get(":id")
>
> ^ gofmt
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/soundcloud/harpoon/pull/13/files#r15592765>.
>