LogstashLogbackSink: Replace log.trace with call to HttpLogWriter.write()

Being able to provide a custom HttpLogWriter for the LogstashLogbackSink and calling the respective write methods instead of log.trace would increase the configurability.

Detailed Description

Replace log.trace in LogstashLogbackSink with calls to a provided HttpLogWriter or the default one

Context

This change enables logging of requests on other levels, such as DEBUG, INFO, etc.

Your Environment

• Version used: 2.2.0

[whiskeysierra]

But passing in HttpLogWriter is probably not the best approach (?), as it supports just a single argumet, and we’re adding two sibling fields to the log statement (the String message and the Marker http).

Since this was the answer to the original issue, I’ll close it now. We can continue the log level discussion here or create a new issue to track it.

[skjolber]

Would you consider making it configurable again? If someone already is doing a lot of logging and want to add request-/response logging, they might want another level than trace (i.e. info is fair) so it fits in with their current global log level (which is usually debug or info).