4/13/2016 8:35:58 AM
stacktraces in logs
They don't add much value.
Signed-off-by: Pierre-Alexandre Meyer <pierre@mouraf.org>
|
4/12/2016 7:31:01 PM
Pierre-Alexandre Meyer <pierre@mouraf.org>
|
4/12/2016 5:34:38 PM
Pierre-Alexandre Meyer <pierre@mouraf.org>
|
4/12/2016 5:00:42 PM
Pierre-Alexandre Meyer <pierre@mouraf.org>
|
4/12/2016 4:58:21 PM
needs to access the exception mappers to get
the returned status code. To prevent double logging, wrap the response
in a LoggingResponse which will log the exception when the entity is retrieved.
Signed-off-by: Pierre-Alexandre Meyer <pierre@mouraf.org>
|
4/12/2016 4:57:04 PM
and PaymentOperation
Signed-off-by: Pierre-Alexandre Meyer <pierre@mouraf.org>
|
4/12/2016 4:55:37 PM
Pierre-Alexandre Meyer <pierre@mouraf.org>
|
4/12/2016 2:33:16 PM
in logs
This is a proposal to use the Mapped Diagnostic Context (MDC) to print
the accountRecordId and tenantRecordId in logs: http://logback.qos.ch/manual/mdc.html
The MDC is cleared after each request and updated each time an internal context
is created.
This also:
* Switches the requestId implementation to using the MDC rather than a Converter
* Adds the X-Forwarded-For header in the logs (useful when Kill Bill is deployed behind a load balancer)
If we decide to go ahead with this approach, more work is required to make sure
the MDC is correctly passed through to children threads (e.g. when going to plugins).
Signed-off-by: Pierre-Alexandre Meyer <pierre@mouraf.org>
|
4/12/2016 2:24:36 PM
Pierre-Alexandre Meyer <pierre@mouraf.org>
|
4/12/2016 11:39:37 AM
Pierre-Alexandre Meyer <pierre@mouraf.org>
|
