In our codebase, we push RequestContext and immediately run some code with try-with-resources.
For example:

try (SafeCloseable ignored = ctx.push()) {
    logger.trace(decorate(msg));
}

If RequestContext provides run(Runnable) or call(Callable) we can reduce boilerplate code and simplify it.

ctx.run(() -> logger.trace(decorate(msg));

This is inspired by g

Is your feature request related to a problem? Please describe.
I want to use ETCD's ttl, and I noticed that there are some lease methods (LeaseGrant and so on) exposed from client, but I can't figure out how to use them.

Describe the solution you'd like
Add some usage examples in README.md.

Thank you for your creating the great client again.

`[info] ProtocolUtilTest:
[info] generateProtocol
[info] - should generate a protocol with valid format
[WARN] [10/18/2017 10:55:52.375] [pool-7-thread-6-ScalaTest-running-PredictorFSMTest] [akka://EngineFSMTest/user/$$d] Engine is unavailable, not possible to perform event any message in state Unavailable/NoModel
[INFO] [10/18/2017 10:55:52.736] [pool-7-thread-1-ScalaTest-running-GenericHttpA

Is your feature request related to a problem? Please describe.
currently all message have to be specified at start

Describe the solution you'd like
read from stdin line by line, parse messages and send to stream

Describe alternatives you've considered
none yet

Describe why you think this feature is useful for gWhisper users
full streaming support

Should be pretty easy to hook into this. All the client configurations use the default registry. See the easy push example in the link here:

https://godoc.org/github.com/prometheus/client_golang/prometheus/push

In addition to adding support for the push gateway, let's also add some metrics to understand where failures are happening in our indexing funnel. This will require the addition of so