Adding trace-level log info to HTTP spans

[eyalkoren]

I added all in TRACE level. We ask for DEBUG logs frequently, we don't want a per-request/http-exit logging.
If you have any ideas for additional info we may be interested at - let me know.

[ghost]

💚 Build Succeeded

Expand to view the summary

Build stats

• Build Cause: [Pull request #1425 updated]

• Start Time: 2020-10-05T13:51:46.988+0000

• Duration: 49 min 32 sec

Test stats 🧪

Test	Results
Failed	0
Passed	1564
Skipped	12
Total	1576

[SylvainJuge]

lgtm.

[minor] do we really require the isTraceEnabled() call first with slf4j for those cases ?

[eyalkoren]

do we really require the isTraceEnabled() call first with slf4j for those cases ?

I used it where a toString may be invoked otherwise, to spare the related (potentially multiple) allocations. Didn't look in all implementations though, possibly it is never called if the logging level does not qualify...

Update: looked it up - the check is not required for the toString resolve (as expected), but still worth the check when using with multiple message format variables (varargs API), to avoid the Object array allocation.