Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

jenkins test it

@urso We counts for reconnect attempts now.

@urso I need some pointers for how to create the identifier.

The state enum should probably go into the Connection type ?

@agathver The team is at Elastic{ON} / All hands this and next week so it will take some time to respond.

Any updates on this?

The counting looks fine.

It would be nice to have an identifier in general. It's the client knowing about the actual endpoint/ID in use. Let's add the identifier to the output.Client.

type Client interface {
        String() string // alternative names: ID(), Name(), Endpoint(), Target()
	Close() error
	Publish(publisher.Batch) error
}

I used the String() method, as this way the client can be pushed as parameter to the logging functions.

The console output will return "stdout", the file output the path and the network based outputs the url/host/port.

@urso, Added identifiers for connections.

I have used a composition-like approach for naming (borrowed from the convention in ReactJS), in tune with how most clients are being used.

Example, a redis client wrapped with a failover will be failover(redis://10.0.0.1, redis://10.0.0.2)
Default ES config gives backoff(elasticsearch(http://localhost:9200))