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.
Eek! Thanks for the catch.


On Tue, Jul 29, 2014 at 4:22 PM, Peter Bourgon <notifications@github.com>
wrote:

> In harpoon-agent/logs.go:
>
> > +			containerLog.nextListenerID++
> > +			msg.listenerIDResult <- listenerID
> > +		case logActionDropListener:
> > +			delete(ls.getContainerLog(msg.
> containerID).listeners, msg.listenerID)
> > +		case logActionExit:
> > +			return
> > +		}
> > +	}
> > +}
> > +
> > +func (ls *LogSet) getContainerLog(containerID ContainerID) *containerLog {
> > +	x, ok := ls.logs[containerID]
> > +	if !ok {
> > +		x = newContainerLog(containerID, ls.bufferSize)
> > +	}
> > +	ls.logs[containerID] = x
>
> Should only do this within the if !ok block...
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/soundcloud/harpoon/pull/13/files#r15525280>.
>