Right, either is good. Although even if the plugin logs an error, it 
might be nice to have a shutdown message that says "Heka shut down due 
to <plugin> failure" or something.

On Wed May 15 09:35:58 2013, Ben Bangert wrote:
> In pipeline/pipeline_runner.go:
>
> > +
> > +		// Are we supposed to stop? Save ourselves some time by exiting now
> > +		if globals.Stopping {
> > +			return
> > +		}
> > +
> > +		// If its a lua sandbox, we let it shut down
> > +		if _, ok := foRunner.plugin.(*SandboxFilter); ok {
> > +			return
> > +		}
> > +
> > +		// We stop and let this quit if its not a restarting plugin
> > +		if recon, ok := foRunner.plugin.(Restarting); ok {
> > +			recon.Cleanup()
> > +		} else {
> > +			globals.ShutDown()
>
> A Shutdown message, or have the runner's drop an error. If the runner
> drops an error, the LogError takes care of indicating which plugin
> threw the error as well which seems handy.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/mozilla-services/heka/pull/177/files#r4238493>.
>